fbshipit
git-subrepo
Our great sponsors
| fbshipit | git-subrepo | |
|---|---|---|
| 2 | 19 | |
| 387 | 3,125 | |
| - | - | |
| 6.4 | 2.6 | |
| 11 months ago | about 1 month ago | |
| Hack | Shell | |
| MIT 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.
fbshipit
-
Monorepo advice
https://github.com/facebook/fbshipit - copy commits from one repo to another
- Fact: Facebook was first written on PHP
git-subrepo
- Git-Subrepo: Git Submodule and Subtree Alternative
-
Monorepo advice
git-subrepo - complicated and difficult to understand
-
is there any way to combine old repositories into onto one repo?
I find the following approach more consistent to manage components: https://github.com/ingydotnet/git-subrepo . And native package management systems, like npm in JavaScript universe, superior to either of the above. But the choice of a particular method depends on problems we need to solve. In terms of one-time codebase aggregation method they are all equally fine.
-
Git Commands You Probably Do Not Need
I much prefer https://github.com/ingydotnet/git-subrepo
- Git-Subrepo – Git Submodule Alternative
-
Just Use a Monorepo
Where I work we just package everything (nugets, python packages, npm) on our Artifactory. Contracts dependencies (DLLs, protobufs) are also distributed as packages. We made it easy to fetch and test the source and allow developers to develop, debug and test those dependencies with their own project if needed.
Every time we try to assemble repositories in macro-repos we always end up regretting it. Multiple dedicated repositories allow autonomy for teams and enforce modularity and coding as a library. Monorepos have a tendency of becoming huge merge trains easily and often derailed and with lots of fear of being blamed on stepping on someone else's toes.
We update often all our projects knowing full well that not doing so is just borrowing development time at high interest rate.
As a side-note when we do have to do an assembly of different code base, we use git-subrepo: https://github.com/ingydotnet/git-subrepo which provide the best of both submodules and subtree.
-
How to get yaml from upstream repo into monorepo
v2: I use git subrepo or a similar tool, to get the upstream yaml into my repo.
-
Do you use git-subrepo?
I found git-subrepo: https://github.com/ingydotnet/git-subrepo
-
Using Git Subtree vs SubModule?
You might also check out git subrepo.
-
Show HN: Get rid of Git submodules and never look back (now for GitHub users)
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.
What are some alternatives?
hack-codegen - Library to programatically generate Hack code and write it to signed files
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.