back

by jotaen·2y ago·view on hn ↗
> Josh combines the advantages of monorepos with those of multirepos by leveraging a blazingly-fast, incremental, and reversible implementation of git history filtering.

It might be just me, but I have some serious trouble to understand what this actually is, and how I would use it specifically.

From the homepage, I understand that this is some sort of utility around working with git histories in mono repos. But is Josh a client-side CLI tool? Is it a convention for structuring mono repos? A web service? A complete VCS? Or some combination of all that?

1 comments
It works by creating a proxy git remote which transparently rewrites history in ways that keep both sides in sync.
Transparently in the "I don't have to worry about it" way?

Or transparently in the "when something goes wrong I'll have no way to tell what happened" way?

Well, if something goes wrong you tend to have multiple repos that at worst will be recoverable with some amount of lost history. Benefit of Git being a DVCS.

For most of the time you don't have to worry about it other than when you initially set things up.

It's almost always one then the other, no?