Configuring larger runners for default setup

Provisioning organization-level ejecutores más grandes for default setup

1. Add a ejecutor más grande to your organization. See Administración de ejecutores más grandes.

   • To add a custom label to your ejecutor más grande, give the runner a name that matches that label. You can use this custom label when you configure default setup with ejecutores más grandes.

2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your ejecutor más grande. For information on granting only select repositories access to a ejecutor más grande, see Administración de ejecutores más grandes.

3. You can now configure default setup for your organization and repositories, and your ejecutor más grande will automatically pick up code scanning jobs. For more information on configuring default setup, see Configuring default setup for code scanning and Establecimiento de la configuración predeterminada para el examen de código a gran escala.

Extra steps for Swift analysis

Currently, Swift analysis is not available on ejecutores más grandes for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a ejecutor más grande provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on ejecutores más grandes and analyze Swift, you have two options:

• Provision a self-hosted macOS runner with the code-scanning label in addition to your ejecutor más grande. For more information, see Agrega ejecutores auto-hospedados.
• 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