News for hackers. Stuff that matters.
Re:How do people manage hundreds of Git repositories? by zeveb on Wednesday October 04, 2017 @05:58PM (#15405078)
It's too late for you, but I think that it's useful for other folks to see your example and realise why multiple repos are a bad idea.

In the general case, each organisation should have a single repo containing all of its code. There are times to violate this rule, but unless you're in extraordinary circumstances, more than a dozen repos in an organisation is an extremely bad mistake.

Re:How do people manage hundreds of Git repositories? by allwein on Thursday October 05, 2017 @11:17AM (#15409853)
Can you elaborate on this a bit? What are the advantages to keeping everything in a single repo for the organization vs. a different repo per project?
Re:How do people manage hundreds of Git repositories? by zeveb on Thursday October 05, 2017 @03:12PM (#15411797)
Basically, having multiple repos means that one person can change a dependency of someone else's code without fixing the dependent code. This is unavoidable with independent organisations, but is easily avoidable within an organisation which uses unit & integration testing within a single repo (the use of a single repo means that a suite of changes may be applied atomically).

In general, a process which allows one person in an organisation to stymie another's progress is a broken system.