3 ms·
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, eac
by zeveb 9y ago
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.
- allwein 9y agoCan 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?
- zeveb 9y agoBasically, 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.
- kadirt 9y agoYour argumentation feels very flawed. Having multiple repos is a good thing. You have an abstraction, you only get relevant branches/tags for each project. The code commits and pulls faster. You can add project based permissions. Hooks can automatically test each new branch. And maybe you do want keep some of the projects with dependencies on old sdk's. The management required to keep it working sounds horrible