Configuring larger runners for default setup

Provisioning organization-level executores avançados for default setup

1. Add a executor avançado to your organization. See Gerenciar executores maiores.

   • To add a custom label to your executor avançado, give the runner a name that matches that label. You can use this custom label when you configure default setup with executores avançados.

2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your executor avançado. For information on granting only select repositories access to a executor avançado, see Gerenciar executores maiores.

3. You can now configure default setup for your organization and repositories, and your executor avançado will automatically pick up code scanning jobs. For more information on configuring default setup, see Configuring default setup for code scanning and Como definir a configuração padrão da verificação de código em escala.

Extra steps for Swift analysis

Currently, Swift analysis is not available on executores avançados for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a executor avançado provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on executores avançados and analyze Swift, you have two options:

• Provision a self-hosted macOS runner with the code-scanning label in addition to your executor avançado. For more information, see Adicionar executores 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