Now the only activity I see is the one related to the repo I'm working on and the rest of the repos are just left alone. There you'll find a box named Check default remotes for updates every XX minutes. So the thing was telling SourceTree something like do not do anything I don't explicitly tell you to do AKA leave my old code alone.Īnd fortunately the possibility is there: Click the menu Tools | Options then select General and navigate to Repo settings. I just want those files to rest in a deep forgotten dir and nothing else. I don't really know the reason, but I really don't mind, they are just dead code. Not only they came to life, but they came to life every 10 minutes!!!!!įor some reason two of the old repos have some kind of connection to something connected to microsoft. The old unused forgotten repos of inactive dead projects are still being recognized by SourceTree (maybe because it's importing some old config file or so) and suddently things that were dead 3 or 4 years ago, came to life. ln -s MyPreferredKey bbusername-Bitbucket. In my case, I wanted to re-use keys across different accounts and used the following: cd /.ssh. I'm using SourceTree v3.x but it seems that years ago we had SourceTree v1.x in this computer. Agree with Stanislaw and Anthony, symlinks worked great for me, but I did have to reboot my computer for it all to work seamlessly within SourceTree. Having 3 or 4 repos could mean something normal, but it detected about 100 repos in my computer. One of the things I observed is that SourceTree insists in making a "for each" of aaaaaall the repositories that it knows and make real internet connections for all of them. The look of this window is similar to this: Leaving this window open for 10 or 15 minutes, you can see there's a huuuuuuuuuge enormous amount of background things going on in the process. opens a separate window which displays the activity log. You can now do al the GIT actions you desire from your happy little SourceTree interface.Clicking the Menu Tools | Process Viewer. You’re now back in SourceTree, and the app should show the connected account.In the dialog that says “Do you want to allow this page to open SourceTree?”, answer with “yes”.If not already done, login into your GitHub account.If all you want is a safe and quick way to connect SourceTree with GitHub, follow the next steps: This post isn’t about all the benefits and security aspects that come with using your GitHub account via HTTPS, SSL, Personal Access Tokens and what not. Now you’ve cleaned up the “authentication attic” that the Sourcetree app has been stuffing. Store them somewhere safe if you’re not sure they can be removed safely If you remove all the files that have “github” in it from the directory, you make sure that SourceTree won’t use those (wrong) authentication setups.You should see some files with formats like:.If you can’t see the Library subdirectory, turn on “view hidden files” using the following shortcut: Command, Shift and Period keys: cmd + shift + 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. authentication attic that the Sourcetree app has been stuffing. Whatever I tried or did, Sourcetree kept on barking at me with a nice red commit failed error: Force push permission is required to delete branches. 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. 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”.The fastest way to get GitHub and SourceTree to play nice
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |