- #Using sourcetree with github mac os
- #Using sourcetree with github manual
- #Using sourcetree with github code
The following steps assume you know what you’re doing and you don’t have a gazillion separate GitHub accounts on your machine to access various accounts / and or repos. What if there were files remaining that messed up with my authentication setup?
#Using sourcetree with github mac os
The Mac OS version of SourceTree saves authentication files on disk. It seemed that whatever I did, the new credentials weren’t picked up. Then I tried reconnecting using a new oAuth account item.
I tried removing my GitHub account under Preferences > Accounts, and using a Personal Access Token that I did setup under my Github account’s Token page. If you are setting up a fresh connection from your SourceTree app with your GitHub account, and you never did this before on your current Mac, you can skip this chapter. And I just couldn’t get them working quickly. Whatever I tried or did, Sourcetree kept on barking at me with a nice red commit failed error: That dream was crushed as recently, I couldn’t commit from SourceTree to a GitHub repository I was working on after a sweet bug fixing session for a client’s app.
#Using sourcetree with github code
Delete the Github authentication files under Home > Library > Application Support > Sourcetreeĭon’t you hate it when you’ve done some very nice programming that implemented that awesome new feature or fixed an annoying bug that caused a crash of your app?Įspecially when it’s late, and you’re like: “let me just commit this version so I can go to bed sleeping like a rose as my code is committed and safe from harm”.I reckon that this solution will also work in situations other than Sourcetree on MacBook only.The fastest way to get GitHub and SourceTree to play nice 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. Apparently, the first occurrence of host * is used for every host, so the github host is shadowed entirely.
#Using sourcetree with github manual
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. 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.
0 kommentar(er)
