As someone who's never heard of a metarepo before, I'm still not sure exactly what it is or why I should use it after reading their landing page. I think a metarepo explainer video would helpful.
I am still really happy with using git subrepo as my metarepo <a href="https://github.com/ingydotnet/git-subrepo">https://github.com/ingydotnet/git-subrepo</a>
One of the reasons to have a mono repo is to avoid the mirroring of PRs between repos. If you have 40+ repos and each time a package gets updated and you need to raise 39 PRs to bump the package. It's getting really old to do mirroring etc.<p>Not sure how this is an improvement over using a mono repo
Not sure the implementation details but this<p><pre><code> $ git clone https://josh-project.dev/josh.git:/docs.git
</code></pre>
Seems really neat to me
> Maintaining an open-source library as part of your proprietary codebase? You can use metahead to publish and synchronise part of your code in its own public repo. Accept external contributions and check them against your internal usage of the library. You have the choice to make as much or as little as you want public, with file-granularity filters.<p>I've wished for this in multiple open-source oriented companies.
Looks cool, but I am unsure why I would use this instead of git scalar[0] with git submodule[1]?<p>[0]: <a href="https://git-scm.com/docs/scalar" rel="nofollow">https://git-scm.com/docs/scalar</a><p>[1]: <a href="https://git-scm.com/docs/gitsubmodules" rel="nofollow">https://git-scm.com/docs/gitsubmodules</a>
Hey Metahead. I wonder if you guys would be down to collaborate? We have a project that might plug in nicely. Let me know: sam@less.build<p>Or, feel free to drop a GitHub link?
MIT License<p><a href="https://github.com/josh-project/josh/blob/master/LICENSE">https://github.com/josh-project/josh/blob/master/LICENSE</a>