(Edit Jan-30): After an intensive cleanup at c:\users I re-installed SourceTree and Cloned successfully few repos. It looked fine till I exit ST and re-entered. Then problems began. Please view the enclosed images. repo "su4_emv_pom_shared" intruded into repo "aps_30-beach-main". Check also down the 3rd image message "fatal: refusing to merge unrelated histories".
Hi. Upon any clone-session, SourceTree (3.1.2 but also at the newest version) ends up by showing other (and undesired) repo, regardless which repo I tried to clone.
Not only that, the shown repo is defective (includes invalid commits, detached from master branch).
I've tried these:
- Uninstall ST
- Shift-Del Atlassian folder from its root, at c:\users
- Shift-Del SourceTree folder from its root, at c:\users
- Reinstall ST, including Mercurial, assigned to Bitbucket
- Create fresh pair of HASH keys (SSH Private/Public)
Now get this:
- Clone repo A - ST shows repo Z
- Clone repo B - ST shows repo Z
And so on and so forth.
Any ideas how to solve this irritating problem ? (like Registry editing or deleting other files/folders)
BTW: Cloned using gitk worked like a charm! same thing for $ git clone
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events