Live data from Hacker News

Metahead – An enterprise-grade, Git-based metarepo

metahead.dev

21–30 of 38 posts

Re: Metahead – An enterprise-grade, Git-based metarepo

#21
post #19

Earlier quoted context omitted.

It does, in fact, relate to a repo like a repo relates to a file! Because every projection only contains related history and subtrees – much like if you were looking at a history of a file in a git repository

So I can “commit” a repo containing some history as the new version of a previous repo containing a different history?

You can, if histories are related. They usually are - you add commits on top. Your history will be reverse-transformed in such a way so that its impact on the whole metarepo can be assessed. So if you modified a file in a library that ten other applications depend on, those applications would get this modification applied and would trigger a CI run to verify your change.

Re: Metahead – An enterprise-grade, Git-based metarepo

#24
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

Re: Metahead – An enterprise-grade, Git-based metarepo

#25
post #13

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.

Vlad from metahead here. We answer this in the FAQ – metarepo is just a git repo that you can slice and dice any way you want while preserving history and having the ability to work on your part of the code. We went with "meta" because it's not exactly mono- or poly- – it's flexible enough so that you can make anything out of it. It also stores information about how your repos / projections relate – in that sense it'…

[dead]

Re: Metahead – An enterprise-grade, Git-based metarepo

#26
> 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.

Re: Metahead – An enterprise-grade, Git-based metarepo

#27
post #11

MIT License https://github.com/josh-project/josh/blob/master/LICENSE

Can you please stop posting these? I'm sure your intention is good but anything as repetitive as https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... is off topic on HN.

You've also posted some good unpredictable comments so I definitely don't want to ban you. Basically, any form of predictability is what we're trying to avoid here.

Re: Metahead – An enterprise-grade, Git-based metarepo

#29
post #13

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.

Vlad from metahead here. We answer this in the FAQ – metarepo is just a git repo that you can slice and dice any way you want while preserving history and having the ability to work on your part of the code. We went with "meta" because it's not exactly mono- or poly- – it's flexible enough so that you can make anything out of it. It also stores information about how your repos / projections relate – in that sense it'…

It's... a materialized view? There's a great big ur-repo back there somewhere, and your tool provides multiple views into it?

Hoenstly, that's a neat idea. No use to me, but a neat idea.

Post reply on HN