Connect your GitHub organization
Before any workflow can use runs-on: craci, CRACI must be connected to your GitHub organization. The connection is a GitHub App installed on your org; it lets CRACI run workflows from the repositories you select.
Connect
Section titled “Connect”- In CRACI, go to Settings → Builds and start the Install GitHub flow. CRACI walks you through creating its GitHub App and installing it on your organization.
- During installation, grant the App access to the repositories whose workflows should run on CRACI (all repositories, or a selected set).
- When the connection reports configured, your workflows can run on CRACI.
The GitHub App is installed once per organization. Re-running the flow is a no-op once the App is installed.
Allow public repositories
Section titled “Allow public repositories”If your organization builds public repositories on CRACI, an organization owner must allow public repositories in the runner group CRACI uses. Until then, GitHub keeps jobs from public repositories queued and never hands them to a CRACI runner, while jobs from private repositories run normally.
- In GitHub, open your organization’s Settings → Actions → Runner groups → Default.
- Select Allow public repositories and save.
New jobs from public repositories then run on CRACI. If a job that was queued earlier does not start, re-run it. Repositories under a personal account don’t need this step.
Updating permissions
Section titled “Updating permissions”To change which repositories CRACI can build, update the App’s installation on GitHub rather than re-running the flow. From your organization’s Settings → GitHub Apps → CRACI → Configure, adjust the repository access (all repositories, or a selected set). The change takes effect immediately.
With the connection live, point a job at CRACI and run a build; see Run workflows on CRACI runners.