Connect repositories
Before a cloud task can work on your code, JetBrains Air Teams needs a connection to the VCS provider that hosts it. You connect a provider once, and from then on the repositories you can reach in that provider are available to your tasks and automations.
You can start the flow yourself from JetBrains Air Teams. In the Air app and in AI Assistant in IntelliJ-based IDEs, the cloud task flow prompts you when access is needed.
What the connection does behind the scenes differs from provider to provider – see Source control.
Before you start
You have access to the repository you want to work on in your VCS provider.
For GitHub organization repositories – the JetBrains Air connection app is installed in GitHub for the organization that owns the repository. A user with administrative permissions in that organization does this once – see Set up organization repository access.
For repositories on a self-hosted GitHub Enterprise Server – the instance is registered for your organization in JetBrains Central Console, and the generated app is installed on the server. An organization administrator does this once – see Set up organization repository access.
For repositories on a self-hosted GitLab Self-Managed – the instance is registered for your organization in JetBrains Central Console. An organization administrator does this once – see Set up organization repository access.
For personal repositories – no extra setup is needed. You authorize the app for your own account as part of the connection flow, and on GitHub you install it for your account at the same time.
Connect a VCS provider
Start the connection flow.
From the web:
In JetBrains Air Teams, go to , find your VCS provider, and click Connect.
From the Air app or AI Assistant:
Start creating a task and select a cloud run environment. See how to do it in the Air app and in AI Assistant. The task flow prompts you to connect the provider when access is needed.
If the JetBrains Air connection app isn't authorized yet, click Authorize and complete the provider's authorization flow.
Authorizing lets the app act on your behalf in the provider, for example, to read code and open pull requests. It doesn't widen what you can reach – you never gain access to repositories you can't already access in the provider.
After the connection is established, the connected provider appears in JetBrains Air Teams under , showing the connected account and the organizations available through that connection.
Finish the flow. What happens next depends on your VCS provider.
GitHub and GitHub Enterprise Server – authorization grants access to your personal repositories but not to organization repositories.
If the task still can't run, read access to the target repository is required. Click Manage to open GitHub and grant the app access to the repository, or request it if you aren't entitled to grant it yourself. See Manage repository access.
Organization owners are notified about the request, but repository admins aren't. If the repository is administered by a repository admin, contact them directly.
GitLab and GitLab Self-Managed – authorizing completes the connection. Cloud tasks can use every repository you can access in GitLab, with no extra step.
A cloud task runs against one repository. If the agent also needs code from another repository, for example shared skills or configuration, clone it from the environment's startup script – see Clone additional repositories.