Authentication is performed using the ssh key, and it asks for the ssh key password every time the source tree is restarted. I am attaching a git repo to the synology nas using gitserver and linking with sourcetree from the client. If you use multilpe accounts to access GitHub or another host the GCM will reprompt each time it changes account. Problem of asking for password every time sourcetree starts when using ssh. ![]() GCM can only store 1 set of credentials fro GitHub and hosts other than bitbucket. There have been issues with the GCM previously with HTTP rather than HTTPS URLs, if possible use HTTPS.Īlso is using Bitbucket try and ensure you are using URLs that contain the username, e.g. Entering them there shoudl mean they are stored correctly. This should trigger the GCM to request credentials. ![]() Then restart SourceTree and open each repository in turn and do a fetch. 3) disable the automatic remote checking of repositories in SourceTree. 2) remove any credentials from git config files. This should trigger the GCM to request credentials. 1) remove all existing git: prefixed entries from the Windows Vault. The credentials for both are stored in the Windows Vault or Credentials Manger, the entries are prefixed with 'git:'ġ) remove all existing 'git:' prefixed entries from the Windows Vault.Ģ) remove any credentials from git config files.ģ) disable the automatic remote checking of repositories in SourceTree ![]() 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.Hi SoureTree for windows now shares credentials with Git via the Git Credential Manager or GCM. 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. I'm using SourceTree v3.x but it seems that years ago we had SourceTree v1.x in this computer. Having 3 or 4 repos could mean something normal, but it detected about 100 repos in my computer. in c:\program files\ etc then simply installing the latest GCM should work as it will update the default GCM in the git install and that GCM will be. ![]() So if you are using SourceTree with a System Git install, e.g. 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. However in the meantime, SourceTree relies on its forked GCM being checked after the default version being used by the git install. The look of this window is similar to this: When Sourcetree keeps asking for password when committing or pushing data to a server, the following solution worked for me: Go to terminal in your project folder and enter: 1. 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. Git / Software Development / Leave a comment. opens a separate window which displays the activity log. Clicking the Menu Tools | Process Viewer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |