![]() I reckon that this solution will also work in situations other than Sourcetree on MacBook only. So I guess that you want to look for the problem in ~/.ssh/config. Even better is to confine github to the correct host too. This works fine and it solved the problem. The following solution solved the problem: Just let the first record refer only to the designated host instead of all hosts: # - ssh naar OUNL - Download free for Windows Manage installations and updates at scale Give your developers the power and simplicity of a Git GUI client in your managed environment. ![]() Apparently, the first occurrence of host * is used for every host, so the github host is shadowed entirely. ![]() ![]() This prompted me to read a manual for the ssh config file. When I swapped both records, ssh to github worked again, but ssh to 145.20.188.96 did not work anymore. IdentityFile /Users/sjo00577/.ssh/id_ou_rsa In my case it contained two records: # - ssh to OUNL. I found out that the ssh configuration file, which is ~/.ssh/config, plays a role in this matter. Instead of trying and erring with lots of different answers, I went after the root cause of the problem. I had the same problem, except the error message I got sounded: Permission denied (publickey,password) Just follow the steps in the answer with "Update Jan 2017" BUT, there's a nice way to fix this from the Apple stack exchange: EDIT: Apparently OSX Sierra made it so you don't get your keys back when you login, so you'll have to do this every time you start your computer. After this you should be ready for a password-less login.Īfter I added my SSH key, SourceTree started authenticating correctly. You will then be prompted for your passcode, which will be stored in your keychain. To add your private key to the keychain simply use the command: ssh-add -K /path/of/private/keyĪs an example if your private key is stored at ~/.ssh and is named id_rsa, you would use the command: ssh-add -K ~/.ssh/id_rsa On Mac OSX, the native SSH client can use the built-in keychain directly. View topic Version control and Sourcetree Get an overview of version control and the role that Sourcetree plays. After you select a Host, enter your hosting details. You can add multiple accounts to Sourcetree. View topic Understand the interface See some of the major parts of the SourceTree interface. Get started Install and set up Sourcetree Connect your Bitbucket or Github account To add repositories to Sourcetree, log in with your Bitbucket or Github account. ::check of one of the params contain a absolute windows pathĮcho.It was hard to find this answer, but it looks like the way to do this is to just add the ssh key to your keychain in Mac OS. Install and set up Sourcetree Find the basic info you need to get working. Setlocal ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION ::this also support calls that contains a absolute windows path (you can use git command in cmd or powershell with this. I've also made a GitHub issue about this:Ĭreate bat file with the code below and add it into your windows environment git with Windows application like GitKraken and such. I could always use the Git CLI, but I'd have the perfect dev environment if it was easier to access my project's. I've resorted to keeping my files on my Windows partition and using docker from WSL, but I'm losing the IO improvements. All the help topics I have found online suggest configuring the SSH client in SourceTree. Even though I can connect fine command line, I cant seem to work with any repo through SSH in SourceTree with the error: Permission denied (publickey). When it is somewhat working, the CPU usage of the Vmmem process would jump just because I've opened the repo and lowered immediately after closing the client. 25 Im trying to connect to GitHub through SourceTree on OS X using SSH. I then used a mapped drive to access it, but often got a "The parameter is incorrect" error, so I couldn't do a whole lot before the client becomes unresponsive and closing itself due to the path being unavailable. Has anyone had any success running a stable git client with a repo with it's files inside WSL? Here's my experience.Īt first I was using the \wsl$ path to open the repository, which wouldn't work because of UNC paths errors.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |