Emelia Smith

Isn't this just executing in a subtree of the repository?

e.g., ```console $ pwd [...]/repo/packages/example-create-react-app $ git rev-parse --show-cdup ../../ $ git st ## develop...origin/develop M package.json M ../react/package.json M ../../scripts/createOrUpdateReleasePR.js $ git ls-files -m -o build/ [lots of files]...

> looks similar: [IgorBabkin@6337040](https://github.com/IgorBabkin/multi-semantic-release/commit/63370405a9ddda48db5443c423f7a51e64584aeb) Honestly, not sure there. How shall we move forwards on this?

> Not sure if this pull-request is still alive... > > > The tests are currently failing because there's a cyclic dependency chain in the tests/fixtures/yarnWorkspaces packages, which, as far...

At some point I'll get back to this (I was actually hacking on semantic-release and MSR the other day, but unfortunately the company that was paying for that effort is...

I've been picking this up tonight, and it's very strange. I think it's a bug in the synchroniser, but I'm not entirely sure. I've been messing around with other ways...

Could there possibly be a bug in the underlying library used in the synchroniser? I note that it's at `0.2.0`, though it may have 92% test coverage. I just can't...

Hey @antongolub, I've ended up taking a step back, and I'm now looking into the viability of adopting [Batching Toposort](https://www.npmjs.com/package/batching-toposort), which is explicitly designed for scheduling work like what we...

@antongolub okay, so, I've had some initial good results with using batching toposort; The tests are broken right now, but I don't think they should've worked in the first place,...

What would be needed to land a change for this? Is it just a matter of a corresponding pull request?