Please update to the latest version of Sourcetree.
This issue is no longer occurring.

ag20993938, mloranger We are unable to reproduce this in the latest version. Can you try this with the latest version?

We experience the same issue using subtrees in SourceTree. When we attempt to pull the subtree, SourceTree hangs on the progress bar. Using same commands and executing them directly in git via command line, git asks for password and completes the pull operation properly.

Also seeing this issue in 1.6.14.0, executing the initial (subtree creation) commands manually in terminal works then linking it in sourcetree creates a Subtrees category in the repository to which sourcetree hangs on interaction through the UI.

Albert, It seems that if you created the original subtree on your machine and pushed it up to Stash, it works fine, but when other try to do it it doesn't work. To be honest, since I submitted this, we have seen it all over the place, so I am not sure that is helpful anymore. Basically, subtrees in SourceTree will hang quite a bit when running commands against a remote, in this case Stash, repo.

We too are experiencing this problem, it seems the git.exe (at least on windows) process is launched and hangs. I wonder if it's waiting for credentials to connect to the remote for the subtree and that's not being passed along to SourceTree.

I second this defect. Subtree support is experimental, at best - it is extremely fragile, and not fit for production use.

1. Subtrees added from the command line are not handled correctly by SourceTree. The subtree remote (if added) is treated as a normal remote, with no knowledge about the required "--prefix" on push or pull. Also, SourceTree quickly hangs when updating the log for this local repo.

2. Subtrees added from SourceTree seem to work decently within the local repo. If the subtree commits are pushed to a remote, and that remote is cloned, SourceTree hangs trying to display the log in the new local repo.

Subtrees is the only current git "module/component" solution we can live with, and the way SourceTree is broken in this respect, basically means that SourceTree is unusable to us.

Hello Mike, I don't understand what do you mean when you say to create the subtree originally.
I can't manage to work with subtrees with Stash and SourceTree, it's always hang.

Something that may be helpful, the systems that are not working are those that did not originally create the subtree. They clone the repo, create the subtree, then attempt to use it. On the system that originally created the subtree, the repo can be completely deleted and cloned again, following the same steps, and the subtree pull/push will work.