Hey HN! Ankit and I (from MergeQueue- YC S21) built Changesets to help coordinate Pull Requests across multiple repos.<p>If your team works on projects where developers have to submit Pull Requests across many repos, you've probably felt the pain of coordinating these groups of PRs so they all merge together without breaking dependencies. Github doesn't have a native solution to this, as it treats each repo as an isolated code base. With ChangeSets you can now group these PRs together so that they can be merged and rolled-back as a single unit of change.<p>If you’re on Github, we’d love to have you try it out! For now we’ve added ChangeSets as a toggle under our existing product (MergeQueue) since it was just lower overhead that way (email founders@mergequeue.com if you already have an account with us and we’ll let you into the ChangeSets beta), but you can sign up to try it directly using this link too: <a href="https://mergequeue.com/?ref=changesets" rel="nofollow">https://mergequeue.com/?ref=changesets</a><p>Let us know your thoughts!
Friendly heads up that there's a fairly well known tool from Atlassian called ChangeSets[1]. Currently a bit over 2k stars on github. It's focus is on helping deal with bumping versions in monorepos.<p>Not mandatory that you change your name at all, but this could be a potential source of confusion.<p>[1] <a href="https://github.com/atlassian/changesets" rel="nofollow">https://github.com/atlassian/changesets</a>
Nice (:
Gerrit has been offering this for some time now, nice to have it for GitHub as well: <a href="https://gerrit-review.googlesource.com/Documentation/cross-repository-changes.html" rel="nofollow">https://gerrit-review.googlesource.com/Documentation/cross-r...</a>
Can this also view all open PRs across multiple repos? One issue I've struggled with with polyrepos is having an organization-wide PR list. Having exposure to the entire org helps with cadence and visibility but PRs are typically silo'ed to the affected repo.