How can we improve Azure DevOps?

Allow organizing/grouping git repositories in a team project

This suggestion is migrated to Developer Community. Please use below link to view the current status.
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.

426 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)
      • Jason Kelley commented  ·   ·  Flag as inappropriate

        +1 Setting up a whole new project to organize repos is too much. Would love to have a way to organize those repos within a project space.

      • Christoph H commented  ·   ·  Flag as inappropriate

        Being TFS responsible for an enterprise company in germany, it is just disappointing to lose discussion with many dev teams on execatly and often only this topic. As many other reported before when comparing with Jira, this funcionality missing is just a killer criteria for the devs to switch to git in tfs. This is a biggest impediment we have while of transforming our 5000+ppl enterprise to TFS ! *verysadface*

      • Anonymous commented  ·   ·  Flag as inappropriate

        A virtual hierarchy (folders), Tags or some other means is irrelevant, even limited grouping support of just one more level would help us extremely

      • 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.

      ← Previous 1

      Feedback and Knowledge Base