![]() Go to the following location home directory > Library > Application Support > Sourcetree.? Here’s the steps on how to clean your authentication mess: If - like me - you have one GitHub Account and one pair of creds, you’re saving to… go on. 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? 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |