I have also tried this by adding my username to the url like so: no luck there either. If I click the error message, it brings up the "Details" dialog, which states the following (twice for some reason): remote: Repository not found. I set up the same ssh key on both websites and loaded the private key in Tools>Option>General>SSH Key. I tab off of that field and it populates the destination path and name fields, but at the bottom of the dialog is a yellow exclamation point with this error: This is not a valid source path / URL I have a repository on Sourcetree connected to two remotes, one on Gitlab and one on Github. Select SSH public keys in the menu that appears. Open your security settings by browsing to the web portal and selecting your avatar in the upper right of the user interface. I can clone/pull/push from the sourceTree interface. Associate the public key generated in the previous step with your user ID. I really dont understand, I generated my ssh key with sourceTree agent and load with 'Pageant', I added the public key on my bitbucket account. It only fails in SourceTree.įurther, it is not bad credentials or anything like that, because I can clone, commit and push to my other non-private repos on github using SourceTree with my github credentials.įrom the "Clone a Repository" dialog I enter the source URL, which looks something like this: Step 2: Add the public key to Azure DevOps. I have full permissions to view and commit to the repo, I can see it online when I log in, AND I can clone just fine with the command line and also via the github desktop application. Another app that I switched to in the meantime works normally. Back in SourceTree, I log into GitHub again using my username and password. I go to GitHub and delete my old public key from my account. I delete both the public and private keys for GitHub from the. Tried using the embedded Git in SourceTree and System Git, to no avail. I remove my GitHub account from SourceTree. Click Load, navigate to your SSH folder, and click the private key. The key has chmod 400, same as before, and its the default key /.ssh/idrsa. From Sourcetree, open the PuTTY Key Generator dialog by going to Tools > Create or Import SSH Keys. Add Remote Account First, click on Add an account. Its happening for Github too, with the exact same repos and settings that worked before. This is the simplest method to connect GitHub with SourceTree. You authorize SourceTree to connect your GitHub account with OAuth. I'm attempting to use SourceTree to clone a private repo belonging to github organization of which I am a part. Connect GitHub Repository with SSH Key Method 1: Connect with Remote Account via OAuth The first method is connecting GitHub with remote account. A similar issue is described here however, my symptoms are a little different and none of the steps there seemed to work. I have gotten it to work mostly: I added the public SSH key to GitHub, the private key to Sourcetree, and I added my remote GitHub Account to Sourcetree.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |