Skip to main content
Configure repository access to create environments from GitHub, GitLab, or other SCM providers. This is required even for public repositories. Skip this if you only need empty environments. Click Add a provider and select a provider:
Provider selection dialog showing GitHub, GitLab, Bitbucket, and Azure DevOps options
Configure the host (or use the default for github.com). To support multiple hosts, add a separate provider for each.
GitHub provider configuration with OAuth toggle and host field
Choose at least one authentication method:
  • OAuth: Easy sign-in through your SCM provider
  • Personal Access Token: Users provide their own PAT
Users authenticate before starting their first environment on the runner.
OAuth configuration dialog showing Client ID and Client Secret fields
Click Save. You can now start environments from repos on the configured host.
Runner details page showing successful setup with repository access configured

​
How authentication works

Users authenticate once per host. Tokens are encrypted and stored for future use. If an admin disables an authentication method or deletes an integration, affected tokens are deleted and users must re-authenticate.