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.
https://developercommunity.visualstudio.com/content/idea/365451/allow-organizinggrouping-git-repositories-in-a-tea.html
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
Check!
(thinking…)
Reset
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 →

    31 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Thorsten commented  ·   ·  Flag as inappropriate

        Did anyone from Microsoft ever commented on this request? This is now five years old...

      • Richard Zaat commented  ·   ·  Flag as inappropriate

        I agree, we currently have >150 GIT repositories in our project, and it is becoming a real pain. Everything else in Azure DevOps can be grouped in some way or the other, except GIT repos. And all I am asking for is a security folder structure, same as with the build definitions for example. So I can have groups of people taking care of their own GIT repos, instead of them needing a project admin to create a new one.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I would say this is needed before the term 'Enterprise Ready' really applies here. Case in point is a cross platform solution with multiple separately maintained and reved modules. At the least I need a way to cleanly segment the Java from the .Net code, but after that there are all the sub components of the system. I would second the notion that I should be able to add repos to a 'folder' and set the rights for all the repos in question to 'inherit' from the base folder settings, etc.

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

      ← Previous 1

      Feedback and Knowledge Base