Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
git-repo
repo - The Multiple Git Repository Tool - (mirror of https://gerrit.googlesource.com/git-repo)
Besides these git x-modules, there are historically three contenders:
git submodules: https://git-scm.com/book/en/v2/Git-Tools-Submodules
git subtrees: https://www.atlassian.com/git/tutorials/git-subtree
git subrepos: https://github.com/ingydotnet/git-subrepo
---
git subrepos work simply by copying your dependency to a subdirectory and committing the changes using one large commit that retains metadata about the update to the subrepo. For that reason, git subrepos aren't symlinks. You don't need to git clone --recursive like with git submodules, and you don't need cross-repo authentication. Updating a subrepo means performing another commit.
Even though git subrepos are the most poorly maintained, the design is simpler.
I wish someone would fork and take over maintenance.
git subrepos are the best.
https://github.com/josh-project/josh
which goes at more-or-less the same problem from the other direction. Josh helps with treating a monorepo as separate repos, as opposed to git x-modules' approach of treating separate repos as one repo. Either way, the idea is to try and get the benefits of both monorepo and multi-repo styles, while avoiding/mitigating the disadvantages.
HN talked about it 11 months ago:
I assume the parent comment refers to this, to save others googling "git repo"..
https://github.com/GerritCodeReview/git-repo