Hacker News Reader

For sure. If you are in a monorepo this solution works but if you have distinct microservice repositories it would help to coordinate pr #827 on repo-A and pr #1092 on repo-B are related and need to ship in a certain order.

Exact problem we've run into at work. We've ended up having to write external merge coordination in order to not break our dev deployments.

How would that work? Commits in different repos aren't ordered relative to one another. I suppose you could have a "don't let me merge this PR until after this other PR is merged" feature, but you could do that with a GitHub Action; it doesn't really need dedicated backend or UI support.

> How would that work?

In practical terms: I manually write a list of PRs, and maintain that list in the description of each of the PRs. Massive duplication. But it clearly shows the merge train.

Who hurt you?

Their manager who suggested that everything be a microservice, but everything depends on each other.

Microservices, by the sound of the original comment

Microservices without a monorepo is hell

They've opted for critical damage.