Let me know what you think on Mastodon, or BlueSky (or Twitter X if you must). You have to use the command line interface instead. So, if you want SourceTree to change password then you can’t do it with the GUI. Ive downloaded the latest update to Sourcetree when I try and login my credentials are not accepted. Enter ‘Git Pull’ and hit return to update the repository My company has a Bitbucket account with Atlassian.Run the ‘Actions > Terminal’ command to jump to the location of the repo on the command line.Open SourceTree and navigate to the repository you want to update the password of.SourceTree version: 3.3. Let me know how this issue needs to be fixed. I'm able to login directly through but not through Sourcetree. The latest version (1.12. The majority of issues in Git Credential Manager for Windows have been fixed in recent versions. The solution is actually quite simple once you realise – but doesn’t use any of SourceTrees dialogs. 19 I'm getting below error while cloning a repo through Sourcetree. After updating SourceTree, go to Tools > Options > Git and click 'Update Embedded Git' to get the latest version (at least 2.14.1). Having Googled how to solve this 3 or 4 times now I thought I’d make a note on my blog so I can more quickly find the solution (hopefully the act of writing it down will mean I won’t have to Google it again). It's worth mentioning this method doesn't work if you have sub repositories and SSH, as it will also try to use a visual studio URL to resolve the sub repositories which will be expected in visual studio format, unless you adapt your subrepo clone urls to visual studio style from the default email protected format. What I mean is, when I change my password SourceTree doesn’t remember the change and so I have to enter it every. We’re also security conscious and so we have to change our passwords every couple of months – however this then breaks SourceTree. As such I use SourceTree a lot to manage my code. We also use the suite of Atlassian products for managing tasks, code, and deployment. I'm quite disappointed with this engineering decision, but even more so, the fact they haven't corrected what I along with most other people on this thread think is an obnoxious interference into how experienced developers work.At work we use Git for versioning our code. In fact, I've also signed up for a small corporate plan on GitHub and have moved most of my new work there instead of BitBucket, so that I can more effectively use GitHub Desktop or their GUI for Pull Request management, something prompted largely due to this irritation. But to be honest, until they restore an ability for me to use MY OWN NAMING CONVENTION for the dozens of ssh keys I have to deal with, I have no interest in giving them another chance. not Back to a PC till Monday so you would need to wait for screenshots ) derHugo. And there under Tools->Options->Git at the bottom you can switch between the bundled and the system git. Good to know symlinks work, should I ever decide to give these guys a chance again. You can additional store the credentials also directly in SourceTree under Tools -> Options -> Authentication. That's the reason I haven't come back here since my original post, until getting another message today from this thread and getting curious. However, this solution will not be feasible usually because it is. There should be a way to specify the location of an existing ssh key!Īnother option, and the one I chose, is to switch to Github Desktop, as I really don't like a software vendor who breaks existing, widely-expected intuitive behavior without warning, and then ignores customer complaints about it for months. Not letting me use my existing ssh key is a recipe for losing me as a customer - I don't like being forced to change the way I work. Why can't I use the ssh key which I want to use? Why isn't this finding my default ssh key like all other programs I have which use ssh, including earlier versions of SourceTree. Now, I see no way to specify this key, it's not being found despite being in the normal location on Mac/Linux systems, and it seems the only way to use ssh is to generate a new ssh key - WHICH I DO NOT WANT TO DO. I used to be able to use this with SourceTree. Now, I get a message "no key found", despite the fact I have ~/.ssh/id_rsa defined, it's in my agent and Apple keychain, and I can use this fine everywhere else. Before, I could pick one of my ssh keys (I have dozens, but mainly use one for work and another for personal Git repos) during setup. It seems there is some change to how the setup and configuration of SSH keys work. I'm on a new project where I have to collaborate with some people on Windows and suggested they use SourceTree, and wanted to re-install SourceTree on my macs so I could help them learn this by demonstration, as I have used this from time to time in the past. I normally use the command line git client to work with GitHub or BitBucket. I just rebuilt my laptop and iMac with clean installs of MacOS Sierra.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |