[deleted]
Ask HN: How to handle 500+ repositories in GitHub?
31–34 of 34 posts
Re: Ask HN: How to handle 500+ repositories in GitHub?
#32I work in an org with a similar setup where there is no name-spacing on git repositories. We end up prefixing the project name with our org name.
ex repo name is: $OrgName + $ProjectName
Honestly, it is not a great solution because the org name has changed a few times and we have repos under 3-4 different naming schemes.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#33Earlier quoted context omitted.
Just out of curiosity, why the move? I'll admit I'm something of a GitLab fanboy, but honestly it's because they keep winning on just about everything in CE vs even the paid alternatives (in my mind).
Fair question -- I wasn't involved in the decision, but my understanding is that GitHub is relatively cheap if you're a C# shop (i.e. you're already paying MS for VS). We had to have some moving pain anyway as teams in different departments were using a variety of different git hosting solutions and there was a wish to consolidate.
Gotcha. Yeah, that was about the only thing I could think of. That's a major reason our company chose GitHub, from what I understand. It's hard to fight the decision when most of the pros and value-adds are much harder to quantify than "this subscription is cheaper." I definitely think GitLab is better value (especially for free) but I can't say I have sat down to even do the napkin math or check out the marketing materials from GitLab.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#34I believe you can do this multiple ways, GitHub allows you to create Teams and Projects and then it also allows you to add Topics to repositories.
1) If you don't want to have access control on your repositories you can simply create a project and link it multiple repositories to it.
2) In a similar vein, another approach without access control is adding a topics to your repositories and then searching them in the GitHub search bar using *topic: your-topic".
3) Finally, if you need to have access controls or permissions on your repositories you can create teams and assign that team repositories.
I am not a professional or corporate user, so please forgive me if any of this not 100% accurate.