This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 447
Recognize when local folder is pushed to team project #27
Comments
Thanks for trying this out! I'll find some time to investigate and see what I can do. I'm using a filewatcher already on HEAD to re-initialize when the branch is changed in the VS Code UI (via the dropdown in the lower-left corner), so maybe I can do something similar here. |
jeffyoung
pushed a commit
that referenced
this issue
Jul 28, 2016
#27 Fix the issue where the extension wouldn't detect that a local repository, after being pushed to Team Services, and not initialize until VS Code was restarted.
jeffyoung
pushed a commit
that referenced
this issue
Jul 28, 2016
#27 Fix the issue where the extension wouldn't detect that a local repository, after being pushed to Team Services, and not initialize until VS Code was restarted.
I pushed the changes needed for this functionality in release 104. Please let me know if you have issues with this scenario again. Thanks @chrisdias |
looks good! |
Closed
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The extension recognizes when a local git repository is also a remote repository in VSTS but it does not recognize when the folder becomes a remote repository unless I change a setting or reload VS Code.
Here's how to repro:
-create a new team project in VSTS, which creates a corresponding git repository
Result
In VS Code (regardless of the pollingInterval setting) the extension never recognizes that the repository is now in VSTS. If you change a setting (e.g. set pollingInterval = 1) then the extension reinitializes and the folder is recognized as a VSTS repo. Alternatively you can refresh VS Code which reloads the extension.
Expected
It would be ideal for the extension to automatically recognize that the repository is now in VSTS. I expected that when the extension polled it would figure this out. Ideally it is instant and I don't have to wait 1-5 min. Perhaps you can have a file watcher for a .git folder.
The text was updated successfully, but these errors were encountered: