josh

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

With regard to repo composition, I have been following this project: https://github.com/josh-project/josh

I haven't had a chance to try it at scale yet, but I've been looking at josh (Just One Single History): https://github.com/josh-project/josh which goes at more-or-less the same problem from the other direction. Josh helps with treating a monorepo as separate repos, as opposed to git x-modules' approach of treating separate repos as one repo. Either way, the idea is to try and get the benefits of both monorepo and multi-repo styles, while avoiding/mitigating the disadvantages. HN talked about it 11 months ago: https://news.ycombinator.com/item?id=27844363 Anyone have experience/updates to share since then, or a comparison with git x-modules?

Also check out josh: https://github.com/josh-project/josh

You don't even need to make a skeleton repo first. By passing `-o merge` as extra option on the push to a non existing view, the merging of unrelated histories will be done by the server. See: https://github.com/josh-project/josh/issues/596

I've not used it extensively, but Josh can probably help here. https://github.com/josh-project/josh It's designed for making multiple Git repos from a monorepo, but I think you should be able to make a skeleton repo that represents your desired final monorepo layout and push your individual repos to the Josh subviews of that repo to combine them all. (A big advantage of this approach over the multiple unrelated histories is that you don't have the mass move commits since Josh will rewrite all history as if the files were always in that folder, so you don't have to worry about history of individual files getting broken.)

There are several ways to do this. Having extensively experimented with all of them I can say that the best are josh[0] (if you need external history continuity) and git subtree[1] (if you just need the commits to remain valid within your repository). [0]: https://github.com/josh-project/josh [1]: https://manpages.debian.org/testing/git-man/git-subtree.1.en...

Yes, there is! We (https://tvl.fyi) have been building Nix monorepo tooling for a while. You can see the current state of our repo at cs.tvl.fyi (+ reviews at cl.tvl.fyi and dynamic CI on tvl.fyi/builds). We use josh[0] to let people clone "just in time" repos with the tooling needed for our setup[1]. We've also started a consultancy (tvl.su) that helps companies move onto this setup, and have customers going for it already. The reasons we've not been making a lot of noise about this are that we have other large projects(like Tvix[2]) taking up time, and also the integration with customers moving to this setup lets us more confidently figure out what parts we need to smoothen for "non-TVL" use-cases. As for using Nix in a Bazel-like way, the common experience with Nix is that language-specific build systems are wrapped. This being possibl