How can we improve Visual Studio Team Services (VSTS)?

Allow organizing/grouping git repositories in a team project

The ability to host multiple git repositories in a single team project was essential to get uptake of git as a source control option for larger teams.

But with this comes organizing those repositories.

We need a way to be able group git repositories perhaps through some sort of virtual folder structure (like adding solution folders) to help navigation when a large amount of git repositories exist in a single team project.

331 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Laurence Evans shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • Anonymous commented  ·   ·  Flag as inappropriate

        Our repositories count is growing. Was looking through UI to find grouping option. Can't believe its not there already.

      • Michelle Boyer commented  ·   ·  Flag as inappropriate

        Would like to do a complete migration from BitBucket to VSTS, but we have 348 repos! Please help us get organized by adding this feature.

      • Stijn Vansevenant commented  ·   ·  Flag as inappropriate

        We need this asap. Our organization is choosing between Bitbucket+Jira and VSTS and not having this functionality is hurting the option for going with VSTS.

      • Richard Zaat commented  ·   ·  Flag as inappropriate

        @Phil Carbone: We use the exact same setup, using areas for our teams and using the same area structure for our iterations, build definitions, queries and within TFVC. It is now really time to be able to leverage this functionality for GIT repos and Release definitions as well.

      • Phil Carbone commented  ·   ·  Flag as inappropriate

        Being able to show them when you are under a certain AREA PATH would be amazing (we already have Areas for organization, being able to associate repos to areas so that it only shows the repo for that area would really help)

      • Stephen commented  ·   ·  Flag as inappropriate

        I'm about to move my org to bitbucket where this functionality has been available for years. We are expanding and need to be able to group projects to clients

      • Philippe commented  ·   ·  Flag as inappropriate

        It took a lot of time for the Développers to turnaround and embrace VSTS for GIT, but now my problem is bringing import tens and tens of repos, without having a way to organize them other that the naming convention. We'd definitely use such a solution.

      • Anonymous commented  ·   ·  Flag as inappropriate

        We're just starting to migrate our SVN repos to VSTS using Git but already this limitation means we will lose the organisation previously enjoyed with SVN..

      • Michael Daw commented  ·   ·  Flag as inappropriate

        I would love to see this. We have a lot of repo's in our project. Right now, we rely on naming convention to organize them.

      • Jaykul commented  ·   ·  Flag as inappropriate

        Just to be sure this is caught: the grouping needs to support permission inheritance. One big value of this to us would be about giving permissions automatically ...

      • Ove Bastiansen commented  ·   ·  Flag as inappropriate

        There should also be a way to "tag" a folder against a team. We have a Team Project with multiple teams, each team has different repos they work on. And a way to "filter" based on team is needed. Also keep the last worked on repo in the code tab based on teams. When I open the web ui as TeamA, I would like to see the same repo as last time, not the repo I used last time as TeamB

      • Chris commented  ·   ·  Flag as inappropriate

        +1 and+700 from our current Git in TFS users.This is such an obvious yet missed need.
        Either a folder structure for the Repos originating at the root or allow git repos to exist in any folder structure (are branches out?) in TFVC.

      • Reed Rector commented  ·   ·  Flag as inappropriate

        Don't forget to allow permissions to be set at the folder level that can apply to all the repos below the folder (so that different groups can have expanded permissions for just their repos). Just do the same thing that is done with the build definitions and folder structure.

      • jkleban commented  ·   ·  Flag as inappropriate

        We have a sandbox top-level project and each employee should be able to have their own folder of their repos within it, accessible to others.

      • John Henderson commented  ·   ·  Flag as inappropriate

        We have over 150 small repositories that currently are stored on a file share using a folder structure to keep things manageable. We're looking at moving this code into VSTS, but I'm not sure how we can make it work without some sort of folder structure.

        We also have many more repositories for other products and would really like to be able to organise those as well.

        Ideally, you'd be able to place repositories into a hierarchical structure, specify the repositories available to different teams, and link repositories to Area Paths.

      • Anonymous commented  ·   ·  Flag as inappropriate

        +1. Because some of our git repositories are shared across teams, I would like to group them by tag.

      • spash commented  ·   ·  Flag as inappropriate

        +1 for the virtual folder structure.
        We created a team project which host reusable components developements. For each component we have a dedicated team into the team project. We may have several repos for one component. There is no way to organize the repos per team/component, everything is flat at the team project level.
        The way we are using it today is to define team permissions for each repos, and using a naming rules for the repository (namespaces à la Java -
        Additional issue is that the drop down does not resize itself for long repository names so it is difficult to select the good repo with it .

      • Gerhard commented  ·   ·  Flag as inappropriate

        Same issue here. We have lots of independent repositories in our team project (storing them in one big repository using submodules is no solution for us). This creates an unpractically long list in the TFS code explorer dropdown. The filter is a nice feature, but a way to organize the repositories in a directory structure would be better. Just a visual way of organizing, like proposed, would be enough for us.

      • Shane Garner commented  ·   ·  Flag as inappropriate

        Just a seems like having repos under an area path would be a reasonable way to group/organize the repos. I would just make sure you can tie work from one team/area path to a repo that exists in another team/area path. Even if it is not area path, some sort of grouping/organization is very much needed still.

      ← Previous 1

      Feedback and Knowledge Base