1

Name your workspace

What its CI is called, here and on GitHub.
2

Create it

It gets separate sign-ins, control plane and runners. Nothing is made in any cloud yet.

Repositories

Where jobs come from

Your code hosts send their jobs to your control plane; the ones that ask for your label run on your runners (in your workflows).

GitHubJobs from acme (all repositories)ConnectedManage
Another organizationIts own private App, on this control plane: its jobs run on the same runners
1

Where is your GitHub?

Where
2

Whose jobs?

An organization you own, or your own username. Not an owner? Copy a note for one
3

Create its App

GitHub makes a private App there, then asks where to install it. It registers runners and reads job events, never your code.

It is named after your CI and the organization. Should GitHub say that name is taken (an App of yours from before), type another on its page: any name works.

GitLabgitlab.com or your own GitLab: jobs from the projects you turn on
1

Where is your GitLab?

Where
2

Make a token

An access token with the scopes api, create_runner, manage_runner. The link has them ticked.

3

Paste it here

Kept in your control plane's secrets. Nothing changes in GitLab until you turn projects on.
More code hostsBitbucket, Forgejo, Gitea and 1 more, coming soon
BitbucketBitbucket Pipelines, on your runnersSoon
ForgejoForgejo Actions, on your runnersSoon
GiteaGitea Actions, on your runnersSoon
Azure DevOpsAzure Pipelines, on your agentsSoon
A demo with made-up data, on SuperCI 0.20.4.Set up yours