Code scanning default setup is now available for self-hosted runners on GitHub.com. To use default setup for code scanning, assign the
code-scanning label to your runner. Default setup now uses
actions/github-script instead of the GH CLI. If your organization has a policy which limits GitHub Actions you will need to allow this action in your policy.
Code scanning sees assigned runners when default setup is enabled. As a result, if a runner is assigned to a repository which is already running default setup, you must disable and re-enable default setup to initiate using the runner.
Larger runners are in beta support, with the limitations that you can only define one single larger runner at the org level with the label
code-scanning, and Swift analysis is not supported.
For more information, see “Using labels with self-hosted runners.”
This is now available on GitHub.com. Self-Hosted runners for default setup are already supported from GitHub Enterprise Server 3.9.