Unable to find path to repository on disk
See original GitHub issueDescription
when I clone repository from GitHub to my computer GitHub Desktop popup error with “Unable to find path to repository on disk”
Version
- GitHub Desktop: 1.1.0
- Operating system: mac OS 10.13.2
Steps to Reproduce
Expected Behavior
Actual Behavior
Additional Information
Logs
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Change Git repository directory location. - Stack Overflow
I used grep to find that in my .git/config file in the [core] section is a worktree variable which holds the absolute path...
Read more >unable to locate repository files on disk - cannot add custom ...
neither on path /srv/gitlab/data/git-data/repositories or in container /var/opt/gitlab/git-data/repositories I am able to see the [GROUP]/NAME , ...
Read more >11 Ways to Fix "The System Cannot Find The Path Specified ...
11 Ways to Fix "The System Cannot Find The Path Specified" Error on Windows · 1. Run Command Prompt as an Administrator ·...
Read more >Git clone or Git push fails to an Azure DevOps repository
Go to the C:\Program Files\Git\bin path on your local disk, and then make a copy of the curl-ca-bundle.crt file. Note. When you install...
Read more >Identifying a repository's ID in Bitbucket Server
The System Administrator permission is required to see the location on disk of the repository. To determine the storage location of a repository...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Quit the “GitHub Desktop.app” first. And push it to the application folder. Then this solution can be solved. Good luck!
Closing due to inactivity. @kcysk if you’re able to fill out the issue template and grab the log files from around the time of the issue we’re happy to revisit this.