Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRefactored Clone Dialog #1787
Conversation
donokuda
self-assigned this
Jul 19, 2018
grokys
added
the
WIP
label
Jul 20, 2018
meaghanlewis
added this to the 2.5.5 milestone
Jul 30, 2018
This comment has been minimized.
This comment has been minimized.
In case it hasn't been considered yet, a potentially "quick & dirty" flow for this is to pop up a modal dialog on top of the clone dialog that give the individual the option to log out. I'd imagine the flow to break down like this:
|
meaghanlewis
modified the milestones:
2.5.5,
2.5.6
Aug 13, 2018
grokys
added some commits
Aug 27, 2018
sguthals
referenced this pull request
Sep 5, 2018
Closed
Development Sprint: October 1st Release #1899
meaghanlewis
and others
added some commits
Sep 5, 2018
This comment has been minimized.
This comment has been minimized.
|
This looks great to me @grokys ! One thing that I ran into was when I wanted to enter the username and repo to clone - ex I authenticated with it, but it didn't actually sign me in and I got an error like this Is it possible to show our Sign in dialog here instead to avoid this from possibly confusing users? |
grokys
added some commits
Sep 7, 2018
This comment has been minimized.
This comment has been minimized.
|
@meaghanlewis hmm yes, I'm not quite sure how to deal with that. If the repository is publicly visible then this clone should actually work. We could make a check to see if we have a connection to the server that the clone is being requested from, but again, the clone may actually work. I notice desktop does the same thing in this situation and shows a login dialog. I'm tempted to say that this is expected behavior. |
jcansdale
approved these changes
Sep 10, 2018
|
Sorry, wrong PR. |
jcansdale
reviewed
Sep 10, 2018
|
Changing |
jcansdale
referenced this pull request
Sep 10, 2018
Merged
Include owner in default path when cloning a repository #1906
This comment has been minimized.
This comment has been minimized.
|
hey @grokys im okay to leave the behavior the same when trying to clone a private repo while signed out of a GitHub account. This might just be an edge case and there is a workaround anyway to sign into the account first and then clone. |




grokys commentedJul 19, 2018
•
edited by meaghanlewis
Refactored the clone dialog, basing it initially on the clone dialog from desktop:
Features
Screenshots
Particularly the URL clone view needs some input from @donokuda.
Scopes
GraphQL requires the
read:orgscope the access the user's repositories. This means that the user will have to log out and back in again to use the clone dialog. The following message will be shown in this case (needs input from @donokuda):Caveats
You currently need to log out and back in because the GraphQL query needs theThis is now implementedread:orgscope which your previous login won't have. Need to implement a "You need to log out and back in again" flow in the dialog for this.Only showing first 100 org repositories because of octokit/octokit.graphql.net#132now fixed.Depends on #1761
Closes #1757