Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[WelcomeUX] 'Clone git repository' errors when new SCM is enabled #18857

Closed
roblourens opened this issue Jan 20, 2017 · 2 comments
Closed

[WelcomeUX] 'Clone git repository' errors when new SCM is enabled #18857

roblourens opened this issue Jan 20, 2017 · 2 comments
Assignees
@chrmarti
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone
February 2017

Comments

@roblourens
Copy link
Member

Testing #18091

  • Ensure new SCM experience is enabled
  • Click 'Clone git repo...'

Error notification says 'Unable to open 'workbench.action.git.clone': Could not resolve any model with provided uri.'
@roblourens roblourens mentioned this issue Jan 20, 2017
Closed
This was referenced Jan 20, 2017
Closed
Closed
@chrmarti chrmarti modified the milestone: January 2017 Jan 21, 2017
@chrmarti chrmarti added this to the February 2017 milestone Jan 30, 2017
@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Jan 30, 2017
@isidorn isidorn added the verified Verification succeeded label Feb 24, 2017
@isidorn
Copy link
Contributor

isidorn commented Feb 24, 2017

I have verified that the clone git repository link is gone
But I would have expected that the git clone link is still there and that it actually works.
In the future we will only use this version of git and we should still have this funcionality in the welcome page

@chrmarti
Copy link
Contributor

It's still there is you disable SCM preview. Stable will ship with it disabled. Adding the link back with the new SCM is on my list.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Milestone
February 2017
Development

No branches or pull requests
3 participants
@roblourens @isidorn @chrmarti