Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Sourcetree thinks my repository doesn't exist. How do I debug this?

When I try to do a fetch with Sourcetree, I get the following error:

git --no-optional-locks -c color.branch=false -c color.diff=false -c color.status=false -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree fetch origin 

remote: Repository not found.

fatal: repository 'https://github.com/theCompany/theRepository/' not found

Completed with errors, see above

 

If I run this command on the command line (less the -c credential.helper=sourcetree part which my command-line git doesn't like), the fetch works fine:

git --no-optional-locks -c color.branch=false -c color.diff=false -c color.status=false -c diff.mnemonicprefix=false -c core.quotepath=false fetch origin

How do I debug and fix this?

2 answers

1 accepted

0 votes
Answer accepted

Hi 😊

that sounds like an annoying problem!

Maybe the credentials that SourceTree uses are invalid? You could try to reset them or switch to the system git client.

This post has some informartion about that: https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-has-invalid-credentials-but-cannot-clear-reset-them/qaq-p/753478

I hope that helps!

Best,
Oliver

I was seeing this problem - in my case it was because my account hadn't given permission  for SourceTree to see  the organization the repository was part of. 

To fix this, on GitHub, go to your settings page, then Applications -> Authorized OAuth Apps. Click SourceTree for Windows (in my case), scroll down and allow access for the Organizations you need

This helped me, thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events