Visual Studio Online + Git integration in Team Explorer doesn't work if the remote for VSO isn't named "origin" - by Thomas Levesque

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 998359 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/11/2014 6:30:55 AM
Access Restriction Public

Description

There is an annoying restriction in Visual Studio Online Git integration: if the VSO remote isn't named "origin", Team Explorer doesn't detect that it's a VSO project and doesn't show the "Builds" and "Work items" pages.

The name of the remote shouldn't matter, as long as it points to a VSO project. I typically name my remotes "vso", "github" or "codeplex", and since I often have several remotes, I don't like having one named "origin" because it doesn't tell me where the remote repository is.

I'm using VS2013 Update 3
Sign in to post a comment.
Posted by Microsoft on 11/3/2014 at 2:08 PM
Thanks for contacting us about this issue. We are already tracking this issue on our internal backlog and we plan to add this feature to the product in a future release.

Thanks,
Matt
Program Manager | TFS Version Control
Posted by Microsoft on 10/11/2014 at 7:12 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.