lite

There are a few tools to split commits from sub-dirs to a branch which you can then push to a public repo/monorepo. E.g. `git subtree`, https://github.com/facebook/fbshipit, https://github.com/splitsh/lite, https://github.com/ingydotnet/git-subrepo. A lot of these approaches though rely on the source-of-truth being the internal company monorepo. PRs are synced internally, merged, and then pushed out. It means that someone outside the organization cannot be a maintainer, and the speed of PR merges is dictated by the available resources inside the company. So I'd argue this is not the right OSS way of doing things. Even if there are two public monorepos out in the open you can have similar problems trying to collaborate, because to modify one line of a package, you may need to pull a huge monorepo and its tooling down. Does anyone have a so

Thanks, but I have reading that they work for smaller orgs as well. e.g. http://www.thedotpost.com/2016/05/fabien-potencier-monolithi... https://speakerdeck.com/fabpot/a-monorepo-vs-manyrepos https://github.com/splitsh/lite https://gist.github.com/morewry/d3419a38d74590493042544d4afa... https://github.com/korfuri/awesome-monorepo I was just hoping to connect some one who has some first hand (recent) experience here. Thanks.

Note that there is a third option: both. You can split up a git monorepo with splitsh[1], and/or pull in & out with git subrepo[2] This gets you the best of both worlds and avoid most of the cons of both, although you do get a new set of cons, like keeping them in sync and ensure tooling works in both places. It's not too bad, though. Make sure you bless one or the other as the source of truth and make the other basically read-only, and add a hook to automatically merge from one to the other. 1: https://github.com/splitsh/lite 2: https://github.com/ingydotnet/git-subrepo

Yup, I think Google & Facebook have this one right, a mono-repo is the way to go. But there are advantages to multi-repos, especially if you're trying to share with clients and/or open source. You can have your cake and eat it too: we use https://github.com/splitsh/lite to update our micro-repos on every commit to our monorepo.