Github-desktop on Pop os use wrong clone address
Opened this issue · 0 comments
The problem
When I installed github desktop it wouldn't clone the repo. and when i checked the log it used the https address instead og ssh . I have set up an key, and when I clone it in a terminal, and afterward drag it to gihub desktop the I can update it.
Release version
Version 2.8.1-linux1
Operating system
OS Version: Pop!_OS 22.04 LTS
Steps to reproduce the behavior
- install github-desktop via apt
- create a ssh key: ssh-keygen -t ed25519 -C "your_email@example.com"
- copy the key to github
- clone a repo with github desktop
Log files
024-06-29T19:29:41.784Z - error: [ui] Failed to look up repository clone info for 'https://github.com/masterqms/convert.git'
Error: Although you appear to have the correct authorization credentials, the masterqms
organization has enabled OAuth App access restrictions, meaning that data access to third-parties is limited. For more information on these restrictions, including how to enable this app, visit https://docs.github.com/articles/restricting-access-to-your-organization-s-data/
at Ke (/home/nikolaj/webpack:/app/src/lib/http.ts:170:11)
at gt.fetchRepositoryCloneInfo (/home/nikolaj/webpack:/app/src/lib/api.ts:642:11)
at Object.clone [as onSubmit] (/home/nikolaj/webpack:/app/src/ui/clone-repository/clone-repository.tsx:665:11)
2024-06-29T19:29:41.785Z - info: [ui] [AppStore.getAccountForRemoteURL] account found for remote: https://github.com/masterqms/convert.git - nsnvglobal (has token)
2024-06-29T19:31:06.174Z - info: [ui] Executing clone: git -c credential.helper= -c protocol.version=2 -c init.defaultBranch=main clone --recursive --progress -- https://github.com/masterqms/convert.git /home/nikolaj/project/convert (took 84.318s)
2024-06-29T19:31:06.176Z - error: [ui] git -c credential.helper= -c protocol.version=2 -c init.defaultBranch=main clone --recursive --progress -- https://github.com/masterqms/convert.git /home/nikolaj/project/convert
exited with an unexpected code: 128.
Screenshots
No response
Additional context
No response