SourceTree should fallback to https if ssh fails (sub-modules)

[Vasanth Prabhakar Murari]

I have a super project which has 4 sub modules. It is a known fact that using ssh + auth tokens for jenkins is a good practice rather than using https + password combo. As a result, I configured .gitmodules with ssh and configured jenkins/git repository with ssh public/private keys. Now, jenkins build environment is setup and it works clean.

But for users who are using SourceTree and rely on https login method, it no longer performs https authentication instead tries ssh and fails as public/private tokens weren't present on their system. I know there is a workaround to let users create tokens and avoid this failure. 

But on the contrary, is it also possible for SourceTree to try https if ssh login fails? Since SourceTree is used by users and not by machines, giving more priority to HTTPS login makes sense right?