SourceTree offers for remote repositories an "extended" configuration" (Menu "Repository" -> "Repository Settings", Select remote repository, Press "Edit" Button ...)
An integration with STASH as well with other hosting providers can be configured there.
What are the benefits of extended SourceTree-Integration with STASH?
There are two places where you can set this: Globally in the last page of the Setup Wizard (can be started from the File menu after installation) and then the extended integration gets automatically filled in for all repos cloned from the Stash server given there or individually as you said.
The first feature only works if you set the global setting in the Wizard(?) or if you add an account in the Hosted Repositories window.
The second only works if the "extended integration" is configured, either globally or just for that repo. (The option is always available, but it gives errors without the extended config.)
The third works always, if you have SourceTree installed.
Hmmm ... I see this are features of STASH-Sourcetree integration - but are they really available due usage of "extended integration" configuration?
So I acknowledge these as STASH-SourceTree integration feature - but I don't see any benefits caused by the "extended configuration" with this features
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