{"meta":{"title":"Selbst-gehostete Runner hinzufügen","intro":"Sie können einem Repository, einer Organisation oder einem Unternehmen einen selbstgehosteten Runner hinzufügen.","product":"GitHub Actions","breadcrumbs":[{"href":"/de/actions","title":"GitHub Actions"},{"href":"/de/actions/how-tos","title":"Anleitungen"},{"href":"/de/actions/how-tos/manage-runners","title":"Verwalten von Runnern"},{"href":"/de/actions/how-tos/manage-runners/self-hosted-runners","title":"Selbstgehosteten Runnern"},{"href":"/de/actions/how-tos/manage-runners/self-hosted-runners/add-runners","title":"Hinzufügen von Läufern"}],"documentType":"article"},"body":"# Selbst-gehostete Runner hinzufügen\n\nSie können einem Repository, einer Organisation oder einem Unternehmen einen selbstgehosteten Runner hinzufügen.\n\n\n> \\[!WARNING]\n> We recommend that you only use self-hosted runners with private repositories. This is because forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow.\n>\n> For more information, see [Secure use reference](/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions).\n\n## Prerequisites\n\nBefore you add a self-hosted runner, you should understand what they are and how they work. See [Self-hosted runners](/en/actions/concepts/runners/about-self-hosted-runners).\n\nAdditionally, you must meet the following requirements:\n\n* You must have access to the machine you will use as a self-hosted runner in your environment.\n\n## Adding a self-hosted runner to a repository\n\nYou 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.\n\nFor information about how to add a self-hosted runner with the REST API, see [REST API endpoints for self-hosted runners](/en/rest/actions/self-hosted-runners).\n\n> \\[!NOTE]\n> Organization owners can choose which repositories are allowed to create repository-level self-hosted runners.\n>\n> For more information, see [Disabling or limiting GitHub Actions for your organization](/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#limiting-the-use-of-self-hosted-runners).\n\n1. On GitHub, navigate to the main page of the repository.\n\n2. Under your repository name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n3. In the left sidebar, click ** Actions**, then click **Runners**.\n\n4. Click **New self-hosted runner**.\n\n5. Select the operating system image and architecture of your self-hosted runner machine.\n\n \n\n6. You will see instructions showing you how to download the runner application and install it on your self-hosted runner machine.\n\n Open a shell on your self-hosted runner machine and run each shell command in the order shown.\n\n > \\[!NOTE]\n > On Windows, if you want to install the self-hosted runner application as a service, you must open a shell with administrator privileges. We also recommend that you use `C:\\actions-runner` as the directory for the self-hosted runner application so that Windows system accounts can access the runner directory.\n\n The instructions walk you through completing these tasks:\n\n * Downloading and extracting the self-hosted runner application.\n * Running the `config` script to configure the self-hosted runner application and register it with GitHub Actions. The `config` script requires the destination URL and an automatically-generated time-limited token to authenticate the request. The token expires after one hour.\n * On Windows, the `config` script also asks if you would like to install the self-hosted runner application as a service. For Linux and macOS, you can install a service after you finish adding the runner. For more information, see [Configuring the self-hosted runner application as a service](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service).\n * Running the self-hosted runner application to connect the machine to GitHub Actions.\n\n### Checking that your self-hosted runner was successfully added\n\nAfter completing the steps to add a self-hosted runner, the runner and its status are now listed under \"Runners\".\n\nThe self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to GitHub and ready to receive jobs, you will see the following message on the machine's terminal.\n\n```shell\n√ Connected to GitHub\n\n2019-10-24 05:45:56Z: Listening for Jobs\n```\n\nFor more information, see [Monitoring and troubleshooting self-hosted runners](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners).\n\n## Adding a self-hosted runner to an organization\n\nYou 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 [REST API endpoints for self-hosted runners](/en/rest/actions/self-hosted-runners).\n\n1. On GitHub, navigate to the main page of the organization.\n\n2. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n3. In the left sidebar, click ** Actions**, then click **Runners**.\n\n4. Click **New runner**, then click **New self-hosted runner**.\n\n5. Select the operating system image and architecture of your self-hosted runner machine.\n\n \n\n6. You will see instructions showing you how to download the runner application and install it on your self-hosted runner machine.\n\n Open a shell on your self-hosted runner machine and run each shell command in the order shown.\n\n > \\[!NOTE]\n > On Windows, if you want to install the self-hosted runner application as a service, you must open a shell with administrator privileges. We also recommend that you use `C:\\actions-runner` as the directory for the self-hosted runner application so that Windows system accounts can access the runner directory.\n\n The instructions walk you through completing these tasks:\n\n * Downloading and extracting the self-hosted runner application.\n * Running the `config` script to configure the self-hosted runner application and register it with GitHub Actions. The `config` script requires the destination URL and an automatically-generated time-limited token to authenticate the request. The token expires after one hour.\n * On Windows, the `config` script also asks if you would like to install the self-hosted runner application as a service. For Linux and macOS, you can install a service after you finish adding the runner. For more information, see [Configuring the self-hosted runner application as a service](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service).\n * Running the self-hosted runner application to connect the machine to GitHub Actions.\n\n### Checking that your self-hosted runner was successfully added\n\nAfter completing the steps to add a self-hosted runner, the runner and its status are now listed under \"Runners\".\n\nThe self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to GitHub and ready to receive jobs, you will see the following message on the machine's terminal.\n\n```shell\n√ Connected to GitHub\n\n2019-10-24 05:45:56Z: Listening for Jobs\n```\n\nFor more information, see [Monitoring and troubleshooting self-hosted runners](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners).\n\n> \\[!NOTE]\n> For security reasons, public repositories can't use runners in a runner group by default, but you can override this in the runner group's settings. For more information, see [Managing access to self-hosted runners using groups](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group).\n\n## Adding a self-hosted runner to an enterprise\n\nIf you use GitHub Enterprise Cloud, you can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization owner can control which repositories can use it. For more information, see the [GitHub Enterprise Cloud documentation](/en/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise).\n\n## Next steps\n\nYou can set up automation to scale the number of self-hosted runners. For more information, see [Self-hosted runners reference](/en/actions/reference/self-hosted-runners-reference#autoscaling)."}