Has there been a change in the Bitrise support for SSH keys for connecting to a repo? I no longer see that option present. I see that you can now add a personal access token to connect via HTTPS but not an SSH keypair. We were using SSH for our previous apps but it seems like that is no longer an option? I can still update the keypair in the app settings of the apps still using SSH but I don’t see how to enable it on a new app. The docs seem to indicate you can choose which method you’d like but I’m not seeing any such way in the settings. Is this a switch in support? It’s probably fine but we would need to switch to using HTTPS instead of SSH for our private Swift Packages if SSH is no longer supported.
Hi @arthur_clark_1 - thanks for reaching out. I have a couple of questions in order to get to the bottom of this:
Can you confirm your repo is in GitHub? If so, how are you connecting your Bitrise app/project to GitHub - via OAuth or the new GitHub App integration?
Our repo is in a private GitHub Enterprise server. I actually just connected via this new integration yesterday to integrate the new GitHub checks workflow.
And to fully answer the question I set up a PAT when creating the app, though I’m not seeing an option to change that after the app is created.
I think I can see the issue: the connection method you see in the app settings depends on which type of repository URL you are using (as shown in App Settings > General, see screenshot). If this is a HTTPS URL you’ll see reference to a PAT in App Settings > Integrations, if it’s an SSH one you’ll see reference to an SSH key instead.
I hope this helps! If you have any more issues/feedback on the GitHub App integration please do let us know.
2 Likes
Aah that totally makes sense, I didn’t consider that. I’ll experiment with that, thanks for the help!
You’re welcome! 