Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Atlassian Community about banner
4,457,698
Community Members
 
Community Events
176
Community Groups

Sourcetree keeps connecting to a git repository that is no longer used

In the past I switched my repository, had two for a while, then removed all traces of the old/unused one.

I've scanned just about every file (Sourcetree settings/app data/.git folder/git settings, windows credential manager etc) and cannot find any trace of the old repository, however sourcetree keeps asking for the password for it (via Windows credential manager, and then when I cancel by a sourcetree pop-up). It is rather annoying as these pop-ups just keep on coming.

1 answer

1 accepted

0 votes
Answer accepted
minnsey Atlassian Team Oct 22, 2018

Hi

I suspect the credential prompts are coming from the Git Credential Manager, being called by Git which is being called by Sourcetree.

Sourcetree will make calls, via Git, to the remote hosts of bookmarked repositories periodically.

Check the contents of the bookmarks.xml and opentabs.xml files in %localappdata%/Atlassian/Sourcetree, they contain the only repositories Sourcetree is aware off.

Many thanks!

I did notice that a few unused repositories were still listed in bookmarks.xml. Even though those repositories did not have a link to the old git repo, removing them from bookmarks.xml seems to have solved the problem. Still it doesn't make much sense, but at least the problem has gone away.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events