The best way to avoid this would be to use SSH but Stash should be able to store your password.
Go to Tools->Options->Authentication and make sure that your hostname, username, and password are all saved there.
Screen Shot 2015-05-04 at 1.33.55 PM.png
I had the same. Very annoying. Finally I figured out it had something to do with my account being remembered twice. As myRepoSiteName.com and http://myRepoSiteName.com ->
remove the second one as short version will be added automatically. It helped in my case. Hope it works for you as well.
Yes - this solved, I had >1 account saved as well.
Add you BitBucket account, use the Oauth verify account - then ensure you only have one BitBucket account - set that one as default - close down SourceTree and start up again - finally the incessant prompt gone - +1 vote for this.
Alas, I tried everything I could think of including the above, wiping completely, reinstalling. Used SourceTree since before Atlassian acquired it. But I've had to switch away.
Any app that prompts the user for a password every few seconds should recommend how to fix the issue along the way.
Found the issue here: https://jira.atlassian.com/browse/SRCTREE-1747
marked as duplicate to this, but the permissions must be private: https://jira.atlassian.com/browse/SRCTREE-1746
Hope they fix it and we can use it again in the future. In the meantime there are lots of other clients.
Brendan, I has the same issue with the Authentication dialog constantly popping up. I managed to fix it by explicitly adding the username to all remote.url configurations.
Hope that helps.
Remove all other authentications section in sourcetree other than git hub.
Then click Add or either go to Hosted repositories(to quickly check if it was successful) and click on edit accounts.
In credentials select OAuth and select refresh token. You will be redirected to bitbucket website and click on Grant access.
Now goto your fresh account in sourcetree and select Set as Default.
Done. Now you should see all your repositories in hosted repositories. It shows login error if it is not successful
I have had a problem that I have had to shut down sourcetree totally on mac (command Q) and restart in order to push. I could then successfully push my changes. Strangely I can always pull changes, only on push did it fail.
I am now experiencing an issue that I have to constantly connect using auth button to push. Lasts about 5 minutes and I have to connect again. I can still pull new changes.
Note I am on Mac. I am not being asked for my Mac Password, it is the actual auth to Bit Bucket that I have to sign on to, I am using google Auth. I did have github sign on as well. I removed this and my original bit bucket account then reinserted. No difference. Given it is mac password it is not issue 1947.
As noted elsewhere 1946 is private, cannot review for similarity.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot