git-meta
VFSForGit
git-meta | VFSForGit | |
---|---|---|
2 | 24 | |
216 | 5,944 | |
0.5% | 0.4% | |
0.0 | 4.7 | |
over 1 year ago | about 2 months ago | |
JavaScript | C# | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-meta
- We Put Half a Million Files in One Git Repository, Hereβs What We Learned
-
Git is my buddy: Effective Git as a solo developer
I think it very much depends how you use them. A great option to manage submodules is TwoSigma's "git-meta" https://github.com/twosigma/git-meta.
There's also just "meta" which is a cleaner way to approach the functionality of submodules https://github.com/mateodelnorte/meta.
VFSForGit
-
Debian Git Monorepo
It's not only Windows that uses Git at Microsoft, but Sharepoint and Office (which includes the on-prem version of SharePoint). In terms of repo size Windows and Office are similar. I was part of the team that migrated Sharepoint from a Perforce clone to Git and helped build the tooling to allow Office to move as well. VFS for Git [1] and Scalar [2] are really good pieces of software.
[1] - https://github.com/microsoft/VFSForGit
[2] - https://github.com/microsoft/scalar
-
Serving a Website from a Git Repo Without Cloning It
Congratulations! That means you basically figured out how the clone procedure works and found a way to do so just in a partial way (also in an unsafe way). But it is a cool idea, nonetheless.
Also check out the Scalar [1] project and its predecessor, GVFS [2], both from Microsoft to manage their monorepo via a VFS layer.
[1]: https://github.com/microsoft/scalar
[2]: https://github.com/microsoft/VFSForGit
-
We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
VFS for Git is still Open Source: https://github.com/microsoft/VFSForGit
Microsoft's blog posts have indicated a move to use something as close to off-the-shelf git as possible, though. They say they've stopped using VFS much and are instead more often relying on sparse checkouts. They've upstreamed a lot of patches into git itself, and maintain their own git fork but the fork distance is generally shrinking as those patches upstream.
-
Why SQLite Does Not Use Git
https://github.com/microsoft/VFSForGit
better than it used to, with the caveat that git in particular is not and has never claimed to be good at versioning blobs.
-
π πΎ Oxen.ai - Blazing Fast Unstructured Data Version Control, built in Rust
Oh dear you're not going to like this.
-
He is very conservative...
Itβs virtualised file system: https://github.com/microsoft/VFSForGit, only downloads what you actually use. Same thing in every large company, but different implementations.
-
FYI: LLVM-project repo has exceeded GitHub upload size limit
This is where something like VFSForGit[0] helps out. Instead of cloning the entire repo, it creates a virtual file system and fetches objects on demand. MSFT uses it internally for the Windows source tree (which now exceeds 300GB).
[0]: https://github.com/microsoft/VFSForGit
-
Created a Small Program To Display Upcoming Assignments On My Desktop
There's also a performance consideration. Not excluding /bin/ or /obj/ folders means dependencies are being tracked as well, and sometimes dependencies themselves are bigger than the program's source code itself. This is commonly the case with node projects, as the node_modules folder can balloon to hundreds of megabytes. They should never be tracked in git due to the nature of how git's internal database works. For e.g. if you delete a dependency because it's no longer needed, you can never fully reclaim that disk space (at least for the master branch) as git will need to keep the binary data stored in its internal tracking database because a previous commit in the master branch has captured the data. As you make more branches, git needs to store the data required to reconstruct your repo to a different state when you switch branches. When a branch has changes measured in the kilobytes, check out is very manageable, but when the differences balloon to many MBs due to the presence of heavy binary files, then checkout between different branches/commits can get very slow. Though, this happens anyway when source code data eventually reaches a certain threshold, beyond the hundreds of megabytes, it's made unnecessarily worse by including any binary files. It's one of the reasons Microsoft created VFS for git: https://github.com/microsoft/VFSForGit.
- Meta releases Sapling, a new way of using source control
-
Software for managing config files
You mean like VFSforGit? Or the successor for that called Scalar? This has been a solved problem. Microsoft moved their entire Windows codebase to git. There have been a ton of huge improvements to performance as a result of that. And the above two plugins are easily better ways to deal with what you're referring to without resulting to dead tech.
What are some alternatives?
meta - tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo?
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
EdenSCM - A Scalable, User-Friendly Source Control System. [Moved to: https://github.com/facebook/sapling]
fast-repo - Perform quick actions on one or many repositories π π
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
sourced-repo-mongo - mongo data store and repository for sourced-style event sourcing models
git - A fork of Git containing Microsoft-specific patches.
dvc - π¦ ML Experiments and Data Management with Git
Voxlap - Making Ken Silverman's "Voxlap" voxel graphics engine run on any platform with SDL.
mvfs - ClearCase file system