Metahead – An enterprise-grade, Git-based metarepo

Re:Metahead – An enterprise-grade, Git-based metarepo by vlad_ivanov on Wednesday January 10, 2024 @07:02PM (#38945435)

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's "meta" as well.

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by layer8 on Wednesday January 10, 2024 @07:06PM (#38945466)

“Meta” would normally mean that a metarepo relates to a repo like a repo relates to a file. That would imply an orthogonal versioning axis, similar to a bitemporal database.

I find the term confusing here because that’s not really what it is (if my understanding is correct).

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by vlad_ivanov on Wednesday January 10, 2024 @07:09PM (#38945489)

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

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by layer8 on Wednesday January 10, 2024 @07:17PM (#38945560)

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

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by vlad_ivanov on Wednesday January 10, 2024 @07:23PM (#38945609)

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.

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by remram on Wednesday January 10, 2024 @07:10PM (#38945503)

Where is your FAQ? I couldn't find it in the first few pages of your websites. No link in the footer either. The only button in your navbar is "about" which is not it.

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by vlad_ivanov on Wednesday January 10, 2024 @07:18PM (#38945566)

It's a bit down on the front page

https://metahead.webflow.io/#faq:~:text=Frequently%20Asked%2...

But we got this feedback - we will make it more visible

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by flir on Thursday January 11, 2024 @12:14AM (#38947991)

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.

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by vlad_ivanov on Thursday January 11, 2024 @02:54AM (#38949113)

Yes it's exactly how you describe it

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by flir on Thursday January 11, 2024 @03:40AM (#38949459)

Thanks for confirming. I think that's the sweetest new concept I've seen in some time. Kudos.

[ Parent | on HN ]

Re:Metahead – An enterprise-grade, Git-based metarepo by fuddle on Thursday January 11, 2024 @01:53AM (#38948707)

Thanks for the explanation, that helps a bit. I still think a video explainer would be helpful. :)

[ Parent | on HN ]