vlad_ivanov

4 ms·

1.
by vlad_ivanov 3y ago
One thing to note is that we don't bump package versions but rather "mirror" the source code, so in that sense it works like a monorepo. But you're right that PR mirroring doesn't work beyond a certain point, and we
2.
by vlad_ivanov 3y ago
We will add a FAQ entry about scalar and we have one about submodules. But in short, here's why you might want to use this instead of the existing solutions: * sub-repos -- projections as we call them -- are still a part of the one big
3.
by vlad_ivanov 3y ago
Yes it's exactly how you describe it
4.
by vlad_ivanov 3y ago
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 o
5.
by vlad_ivanov 3y ago
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
6.
by vlad_ivanov 3y ago
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
7.
by vlad_ivanov 3y ago
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" be
8.
by vlad_ivanov 4y ago
ACLs are in the works https://github.com/josh-project/josh/pull/561 That being said, the overall scope of permissions and authentication is more complicated, more improvements is definitely needed