Configuring larger runners for default setup

Provisioning organization-level более крупные бегуны for default setup

1. Add a крупное средство выполнения to your organization. See Управление большими бегунами.

   • To add a custom label to your крупное средство выполнения, give the runner a name that matches that label. You can use this custom label when you configure default setup with более крупные бегуны.

2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your крупное средство выполнения. For information on granting only select repositories access to a крупное средство выполнения, see Управление большими бегунами.

3. You can now configure default setup for your organization and repositories, and your крупное средство выполнения will automatically pick up code scanning jobs. For more information on configuring default setup, see Configuring default setup for code scanning and Настройка настройки по умолчанию для сканирования кода в масштабе.

Extra steps for Swift analysis

Currently, Swift analysis is not available on более крупные бегуны for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a крупное средство выполнения provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on более крупные бегуны and analyze Swift, you have two options:

• Provision a self-hosted macOS runner with the code-scanning label in addition to your крупное средство выполнения. For more information, see Добавление локальных средств выполнения.
• 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