We are excited to let you know that we are working on this suggestion. We expect this feature to be released by the end of the year. Not only will you be able to commit to submodules, but you will also be able to view the file history and blame within a submodule.

However, VS will not yet have “full” submodule support; you will only be able to have one Git repo open per VS instance. Therefore, working between a submodule and the parent repo will not be seamless. To help us prioritize further submodule features, please open new UserVoice items.

Kayla Ngan
Program Manager

There have been some delays, but we still have this feature on our backlog. I’m resetting the status to reflect this, but this is one of our top priorities upcoming. Thanks!

We are excited to let you know that we are working on this suggestion. We are pursuing a design that will allow you to set pull —rebase at the global and repo level; the setting will be saved directly to your gitconfig. We will consider rebase on a pull-by-pull basis (as requested in some comments) for future development.

Sync runs pull immediately followed by push, so configuring this setting will allow Sync to do a pull —rebase.

In the event that you are using Visual Studio 2017, you can set up pull —rebase in your gitconfig and VS will already respect those settings.

Kayla Ngan
Program Manager

We are excited to let you know that we are working on this suggestion. We are pursuing a design that will allow you to set fetch —prune at the global and repo level. We will consider prune on a fetch-by-fetch basis (as requested in this suggestion) for future development.

In the event that you are using Visual Studio 2017, you can set up fetch —prune in your gitconfig and VS will respect those settings.

Kayla Ngan
Program Manager

We are excited to let you know that we are working on this suggestion. We expect to release this feature in an update around the end of the year.

Kayla Ngan
Program Manager

We are excited to let you know that we are working on this suggestion. We are designing a tags experience that will not only let you view all of your tags, but also push and delete them.

Kayla Ngan
Program Manager

When the item was marked as completed, we have misunderstood the suggestion. Your suggestion is still valid, and on our backlogs. But we are not actively working on this.

Opening the suggestion again for you to upvote this one. Sorry for the confusion.

Ewald Hofman
VSTS/TFS Program Manager

As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

Ewald Hofman

We’ve actively working on improvements to the pull request platform to enable improved comment tracking when new changes are added in subsequent commits. We have other improvements to the pull request experience underway as well, and you’ll see these changes starting to roll out soon and continue for several sprints.

Thanks,
Matt Mitrik
Program Manager

As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

Ewald Hofman