with ansible
Ask HN: How to handle 500+ repositories in GitHub?
11–20 of 34 posts
Re: Ask HN: How to handle 500+ repositories in GitHub?
#12One feature I REALLY like about ZenHub is that you can build a project board with multiple repositories on it. Easy to tie tickets from the back-end repo to the front-end repo, or whatever you need. Wish GitHub would build out multi-repo projects... or just buy ZenHub. Nice of GitHub to build out their own project boards in recent years, but it's never been as good as some of the 3rd Party tools that are out there.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#13I'm having trouble with 30 or so repos. I shudder to think what 500 or more is like. Search every time? kind of not good.
Maybe there is a place for an "index" repo that holds a set of github pages that acts as an index into all the repos and groups them via that page instead of just using search.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#14I built this command line tool to manage settings and configuration of an org with ~300 repositories: https://github.com/svenmuennich/github-commander
Re: Ask HN: How to handle 500+ repositories in GitHub?
#15I started a new project with monorepo, but soon the number grew when I had to share smaller private sub-projects with smaller teams. I wish there was a way to only share a directory or so.
On the monorepo, I learned a couple interesting things. For example with npm packages, even if you host multiple packages in a single monorepo you can still track dependents for each individual lib [1]. Well done Github.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#16Probably need to think through the concrete use cases for "handle".
e.g. if there are requirements related to tracking issues in some uniform way in software projects that have a many:many relationship with source repos, a possible solution is to use some other system for issue tracking, don't try to track issues in github.
If there's a requirement to uniformly configure access controls / branch protection etc to hundreds of git repos, you could use terraform or roll your own automation using the github API combined with whatever you can enforce at the github org level.
Re: Ask HN: How to handle 500+ repositories in GitHub?
#17I started a new project with monorepo, but soon the number grew when I had to share smaller private sub-projects with smaller teams. I wish there was a way to only share a directory or so. On the monorepo, I learned a couple interesting things. For example with npm packages, even if you host multiple packages in a single monorepo you can still track dependents for each individual lib [1]. Well done Github. [1] https:…
Google “git subrepo”
Re: Ask HN: How to handle 500+ repositories in GitHub?
#18There are github organizations. I checked this year and it allowed to create one for free.
https://docs.github.com/en/organizations/collaborating-with-...
Re: Ask HN: How to handle 500+ repositories in GitHub?
#19I started a new project with monorepo, but soon the number grew when I had to share smaller private sub-projects with smaller teams. I wish there was a way to only share a directory or so. On the monorepo, I learned a couple interesting things. For example with npm packages, even if you host multiple packages in a single monorepo you can still track dependents for each individual lib [1]. Well done Github. [1] https:…
Right, you could reduce the number of projects by grouping related ones as monorepos. I have published a serie of articles on how to create monorepos in JavaScript with Lerna, this is the first part: https://www.adaltas.com/en/2021/01/05/js-monorepos-project-i...
Re: Ask HN: How to handle 500+ repositories in GitHub?
#20I started a new project with monorepo, but soon the number grew when I had to share smaller private sub-projects with smaller teams. I wish there was a way to only share a directory or so. On the monorepo, I learned a couple interesting things. For example with npm packages, even if you host multiple packages in a single monorepo you can still track dependents for each individual lib [1]. Well done Github. [1] https:…
Google “git subrepo”
Great, thank you