Currently, I have a few SVN Repositories, and it looks like this:
Customer1 (this is a proper "SVN Repository") project1 foo82 trunk tags branches bar01 trunk tags branches project2 ... project3 ... ... Customer2 (this is a proper "SVN Repository") tool1 windows-version trunk tags branches mac-version trunk tags branches server-component trunk tags branches ios-app trunk tags branches tool2 (same subfolders as tool1) tool3 (same subfolders as tool1 with slight modifications) Customer3 (similarily complicated folder structure) ... (about 5 more customers) ...
I would like to transition all of that to git, somehow. So, I will probably have a few repositories:
foo82 bar01 tool1-windows-version tool1-mac-version tool1-server-component tool1-ios-app tool2-windows-version tool2-mac-version tool2-server-component tool2-ios-app ... (150 more projects) ...
the problem is now that they are all on the same hierarchy level. I would like to place the git repositories into some hierarchy, like
Customer1 (this is not a repository, just a folder!) project1 (this is not a repository, just a folder!) foo82.git (this is a git repository) bar01.git project2 (this is not a repository, just a folder!) ... (here lie a bunch of git repositories) Customer2 (this is also not a git repository, just a folder!)
Is there a tool that allows me to manage hundreds of git repositories, and lets me categorize the repositories into nested groups? I cannot see how to achieve this, e.g., with GitHub. I would like to be able to define access policies for groups (and not just single repositories). E.g. I would like to say User1, User2 and User3 may read/write to Customer1, and User4-User6 may read/write to Customer2, and User1-User6 may read all repos, and User7-8 may read/write all repos. User9 is admin for everything under Customer2, and User10 is superuser.
I don't care how the repositories are actually stored on the servers filesystem. I'm happy if I just have an interface that pretends that they are neatly organized into groups, and where I can set access policies on whole "folders". If the actual git repository URLs reflect the visible project structure too, it would be nice.
Or any tips on how to be an admin for 100+ git repositories without going insane would be appreciated.