-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding section about VCS #69
Comments
@RedwanFox Interesting idea.
Storing large blobs, in general, doesn't work very well with Git. Though it is more a VCS thing than strictly related to monorepos. Ofc, If you combine it with a monorepo the problem becomes more apparent, and quicker. Let me think about how to potentially wire this into the page. We want to keep it as lean as possible but still informative.
I was actually planning to have some content around this. Git allows you to do sparse-checkouts, and with Nx in particular, you have programmatic access to its project graph. As such you can easily create a script which would allow you to say something like |
It's should be mentioned in context of Git LFS or microsoft git fork with patches especially for monorepos.
Without working VCS you won't get successfully working monorepo and with rising repo size execution times of default commands such as status increase dramatically. https://github.blog/2022-06-29-improve-git-monorepo-performance-with-a-file-system-monitor/ |
Monorepos tend to become very large and optionally have large binary blobs in them (for example art content in gamedev). So different VCS should be considered. For example git as-is is not suitable for large binary objects, etc. Also, it would be great to talk about integration of VCS and build system such as to be able only to checkout folder of particular projects and all of their dependencies.
The text was updated successfully, but these errors were encountered: