SSH keys serve the role of secure transfer between services. In the case of Bitrise, it will ask for your permission to be authorized at your git source provider, for example, GitHub. Read more about how to authorize Bitrise.
The reason behind the need for being authorized, is that Bitrise has to have a working SSH connection to your repository to be able to clone it. There are several ways to make it work. Automatically, by adding it manually, or by using your own key.
Automatic setup ⚓
In the case of GitHub, GitLab and Bitbucket repository setups, Bitrise will generate a public and private SSH key pair and ask whether you like the idea of adding that into your repository automatically as deploy key, or you’d like to add it by hand.
You need admin rights to the repository to be able to auto-add the key to it. In any other case, copy the public key from here and add it to your repository at your provider.
The auto-add option will add the generated key as a read-only deploy key to your repository, it’s the best for your security.
Manual setup ⚓
If you have private dependencies or submodules, you have to add the generated SSH key manually to your profile at your provider instead. That’s because deploy keys are only valid for one repository.
When the system asks if you need to use an additional private repository, click
I need to and copy the key.
Use your own key ⚓
This option can be used if you also have the private key of the given user. You just have to paste the private key and Bitrise will be able to access the repositories.