Configuring larger runners for default setup

Provisioning organization-level größere Runner for default setup

1. Add a größerer Runner to your organization. See Verwalten größerer Runner.

   • To add a custom label to your größerer Runner, give the runner a name that matches that label. You can use this custom label when you configure default setup with größere Runner.

2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your größerer Runner. For information on granting only select repositories access to a größerer Runner, see Verwalten größerer Runner.

3. You can now configure default setup for your organization and repositories, and your größerer Runner will automatically pick up code scanning jobs. For more information on configuring default setup, see Configuring default setup for code scanning and Konfigurieren des Standardsetups für das Codescanning im großen Stil.

Extra steps for Swift analysis

Currently, Swift analysis is not available on größere Runner for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a größerer Runner provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on größere Runner and analyze Swift, you have two options:

• Provision a self-hosted macOS runner with the code-scanning label in addition to your größerer Runner. For more information, see Selbst-gehostete Runner hinzufügen.
• Ensure any repositories containing Swift do not have access to runners with the label code-scanning. Default setup workflows for that repository will only use standard runners