Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
SourceTree keeps cloning the same (and incorrect) repo
Edited
(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