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