Seonglae ChoMonorepos
Design all tools to process at the change level rather than the entire repository (O(change) not O(repo)), ensuring consistency and scalability across the ecosystem
The Ingredients of a Productive Monorepo
So! Suppose you’re an intrepid engineer in a nascent Developer Productivity
team. Your engineering organization has decided that it wants to
move towards a monorepo. You’ve heard the stories
told of Google, Meta, Uber - each a large technology company with
developer productivity organizations consisting of hundreds of engineers -
and you want to capture some of their magic in a bottle and give it to your
users. You wonder - what work lies ahead of you?
https://blog.swgillespie.me/posts/monorepo-ingredients/
Monorepo - Our experience
Nine months ago, we switched to a monorepo. Here is a retrospective on our experience with the switch so far.
https://ente.io/blog/monorepo-retrospective
Git merge history - filter-repo is best for sub directory
Merging packages and their histories into a Lerna monorepo
Update: You probably just want to use lerna import. But if you'd like a manual technique, or aren't actually using Lerna, read on. Let's say you have a Lerna monorepo called acme. You have a package called app, presently in its own repository, that you want to move into repo.
https://stderr.brandonistenes.com/merging-packages-into-a-lerna-monorepo/
sojin.io
https://sojin.io/article/%ED%86%A0%EC%8A%A4%EC%9D%98-%EB%A7%88%EC%9D%B4%ED%81%AC%EB%A1%9C%ED%94%84%EB%A1%A0%ED%8A%B8%EC%97%94%EB%93%9C-%EC%95%84%ED%82%A4%ED%85%8D%EC%B2%98-%EA%B7%B8%EB%A6%AC%EA%B3%A0-%EC%9E%90%EB%8F%99%ED%99%94/
Improve Git monorepo performance with a file system monitor
Monorepo performance can suffer due to the sheer number of files in your working directory. Git’s new builtin file system monitor makes it easy to speed up monorepo performance.
https://github.blog/2022-06-29-improve-git-monorepo-performance-with-a-file-system-monitor/
