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

Cloning an Existing Remote Repo into a new path disables Clone Button. #489

Closed
femisimon opened this Issue Aug 10, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@femisimon

Attempting to clone an existing repo into a folder where the repo has been previously cloned is expected to disable the clone button indicating an error exclamation mark on the path and renaming the folder path where the repo will now be cloned to should re-activate the clone button and allow repo to be cloned. This is currently not happening.

Steps to reproduce

  • Launch Visual Studio and Sign-in to GitHub's extension.
  • Click on clone and select a repo to clone to the default path '' or a new path set as default.
  • Select the same repo to clone; an error exclamation is seen on the link path where repo is to be cloned.
  • Rename path to enable cloning of repo.

Expected result - Clone button should be active and allow repo to be cloned.

Actual result - Clone button remains idle.

  • GitHub Extension version: 2.0.14.2
  • Visual Studio version: 14.0.25424.00

grokys added a commit that referenced this issue Aug 10, 2016

Fix clone base path binding.
It needs to update on every keypress rather than when it loses focus. Fixes #489.

@grokys grokys self-assigned this Aug 10, 2016

@grokys grokys added the bug label Aug 10, 2016

@shana shana closed this in #490 Aug 11, 2016

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