New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to clone Gists in Desktop #2886

Open
cmrberry opened this Issue Sep 26, 2017 · 8 comments

Comments

Projects
None yet
9 participants
@cmrberry
Copy link

cmrberry commented Sep 26, 2017

Description

We have this nifty little button on the top of Gists just like we do for repositories:

screen shot 2017-09-26 at 12 51 51 pm

However clicking that button does not clone the Gist as expected.

Version

GitHub Desktop version: 1.0.1
OS version: macOS 10.12.6

Steps to Reproduce

  1. Go to any Gist, like: https://gist.github.com/jboner/2841832
  2. Click the "Download to Desktop" button that links to x-github-client://openRepo/https://gist.github.com/2841832

Expected behavior: The Gist should be cloned to my Desktop app.
Actual behavior:

  • A user reported that they were taken to desktop.github.com after clicking that button, even though they have Desktop installed.
  • I was unable to reproduce that ☝️ but got an error every time:

screen shot 2017-09-26 at 1 00 52 pm

Note that it doesn't exist, because it won't let me clone it. It's a misleading error message in this case a well.

Reproduces how often: Every time for me.

Logs

2017-09-26T19:57:56.787Z - warn: [ui] Open Repository from URL failed, did not find repository: https://gist.github.com/2841832.git - payload: {"name":"open-repository-from-url","url":"https://gist.github.com/2841832.git"}

@j-f1

This comment has been minimized.

Copy link
Member

j-f1 commented Sep 26, 2017

Does changing the “Local Path’ to /Users/cmrberry/github/latency work? If so, this error occurs because the app is unable to parse a name from the repository URL.

@shiftkey

This comment has been minimized.

Copy link
Member

shiftkey commented Sep 26, 2017

I think this might have been fixed by #2863 which isn't in that build but I'll confirm this is reproducible on master.

EDIT: nope, still reproducible. We should auto-fill the folder name into the path but clearly that's not happening...

@shiftkey

This comment has been minimized.

Copy link
Member

shiftkey commented Oct 6, 2017

@cmrberry this is occurring because we don't correctly detect Gists in the app, so it won't go and create the folder correctly. I thought this was going to be a simple fix, but it looks like this touches a lot of areas - I've opened #2973 to track these tasks.

In the meantime, you can go and edit the Local Path value which will then enable you to clone the repository down.

@shiftkey shiftkey removed their assignment Oct 6, 2017

@DixCar

This comment has been minimized.

Copy link

DixCar commented Oct 9, 2017

I have same problem but
GitHub Desktop version 1.0.3 (latest at this day)
OS Windows 10 Home

@WiliTest

This comment has been minimized.

Copy link

WiliTest commented Aug 23, 2018

I also had a problem with this button.
● The first time it asks to install the app. I did it again (and again) and it asked me to install the app. An hour later it works. I guess it's a cash issue, the page should maybe be reloaded. If that doesn't work open the URL tab of the desktop app and write a link like that: https://gist.github.com/hj78ad2c234565bhds0540sha.git

● then I ran into another problem: "the destination already exist". I gave up.

(I just wanted to delete the previous version of my gist... Why doing it simple when we could complicate it?)

@ssowens

This comment has been minimized.

Copy link

ssowens commented Oct 5, 2018

Consistently getting the following error when I try to clone: "The destination already exists." If I add "latency" as stated above the error goes away. However, why is this happening? Please assist.

screen shot 2018-10-05 at 4 55 36 pm

@aghaynes

This comment has been minimized.

Copy link

aghaynes commented Oct 26, 2018

As @shiftkey previously mentioned, changing the default local name to something meaningful/normal (rather than the long names that github assigns) seems to work.

@theconsultant

This comment has been minimized.

Copy link

theconsultant commented Nov 29, 2018

Changing the default local name to something meaningful worked for me as well.

@shiftkey I don't know if it can be done or not.. but maybe the error message could link to here, or even just tell folks the workaround 'for now' ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment