Clusters: cross-repository review
Last updated .
Can MergeSafe catch a change that breaks another repository?
Yes, with a cluster: you group 2 to 8 repositories that share contracts such as a database table, an API schema or an event, and MergeSafe assesses whether open pull requests in one would break the others.
How a cluster works
- An organization admin creates the cluster in the app and picks its member repositories, 2 to 8 of them.
- Rules name what the repositories share, up to 200 per cluster: database tables, API schemas, events, environment variables, feature flags, HTTP routes, and shared functions or classes.
- The result is a separate Cluster Impact score out of 5 on the pull request, scored like merge readiness and kept apart from it. A pull request with no cross-repository risk scores 5/5.
When it runs
- Only when asked (the default): Run now in the app, or comment
@mergesafe clusteron a pull request. - Every pull request: every new commit on an open pull request in a member repository.
- Pull requests touching a shared contract: only commits that change something another member uses.
- First review only: once per pull request.
Cluster runs are free for now. Anyone who can comment on the pull request can use @mergesafe cluster; see commands. How long cross-repository summaries are kept is on Security and data retention.