by fuddle on 1/10/24, 11:43 PM
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.
by iFire on 1/10/24, 11:07 PM
by wdb on 1/11/24, 12:50 AM
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.
Not sure how this is an improvement over using a mono repo
by edgyquant on 1/10/24, 9:51 PM
Not sure the implementation details but this
$ git clone https://josh-project.dev/josh.git:/docs.git
Seems really neat to me
by rbetts on 1/11/24, 1:10 AM
> 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.
I've wished for this in multiple open-source oriented companies.
by bananskalhalk on 1/11/24, 5:45 AM
by kissgyorgy on 1/11/24, 12:47 AM
You lost me at "enterprise-grade".
by sgammon on 1/11/24, 4:53 AM
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
Or, feel free to drop a GitHub link?
by da39a3ee on 1/11/24, 12:33 AM
Sounds really interesting. I read the whitepaper; it was nice, but it's more like a technically-oriented setting-the-scene than a whitepaper.
by opentokix on 1/10/24, 10:47 PM
What the f is "Enterprise grade"?
by iFire on 1/10/24, 11:10 PM