Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

We couldn't find that repository.

See original GitHub issue

Describe the bug

When cloning a repository (Note that repository is correct), it keeps getting an error. Error will be: We couldn’t find that repository. Check that you are logged in, the network is accessible, and the URL or repository alias are spelled correctly.

Version & OS

Open ‘About GitHub Desktop’ menu to see the Desktop version. Also include what operating system you are using.

Version 2.5.6 and macOS Mojave 10.14.6

Steps to reproduce the behavior

Go to ‘Github Desktop’
Click on ‘Current Repository’
Click the ‘Add dropdown’
Click the ‘Clone Repository’
Type in your ‘URL or username/repository’
Click ‘Clone’
See Error

Expected behavior

I keep getting the error several times and randomly the repository that I want to clone is getting cloned.

Actual behavior

When clicking on the Clone it keeps getting the Error: We couldn’t find that repository. Check that you are logged in, the network is accessible, and the URL or repository alias are spelled correctly.

Screenshots

Add screenshots to help explain your problem, if applicable.

Logs

Attach your logs by opening the Help menu and selecting Show Logs..., if applicable.

Additional context

Add any other context about the problem here.

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

niikcommented, Oct 16, 2020

Hi @danny-xl8, it seems like GitHub Desktop isn’t able to locate your credentials which in turn leads to requests being denied due to hitting the unauthenticated rate limit of the GitHub API

2020-10-14T19:37:53.027Z - info: [ui] [AppStore.withAuthenticatingUser] account found for repository: xl8_pylibs - danny-xl8 (empty token)

Error: API rate limit exceeded. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

Could you please try opening preferences and signing out and then back in again using your GitHub.com account? Hopefully that should allow GitHub Desktop to access the credentials again. If that still doesn’t work please try the workaround for making sure that Desktop is able to access keychain.

0reactions

Tvmpteamcommented, Dec 30, 2020

I am too getting the same issue but i am unable to clone after doing signing off and logging in again. Is there any other way to solve this issue

Top Results From Across the Web

We couldn't find that repository. Check that you are logged in ...

Error will be: We couldn't find that repository. Check that you are logged in, the network is accessible, and the URL or repository...

Travis: We couldn't find the repository - Stack Overflow

The solution was to log out and log in again on https://travis-ci.org.

How to Find the Repository GitHub Desktop Can't Access

– You do not have permission to access this repository. – The repository is archived on GitHub. Check the repository settings to confirm...

Navigating to a repository page shows "We couldn't find the ...

Navigating to a repository page shows "We couldn't find the page you requested" error popup. The following appears in the the browser ...

Integrating my gitHub repository returns "We couldn't find any ...

Solved! On the dashboard page on migrate tab (Travis CI - Test and Deploy with Confidence) you should migrate the repositories. Before migration ......