Trace related repositories in a pull request review
When a change crosses repository boundaries, inspect the related repositories in its review to see which code Proofline selected and which reads succeeded.
How reviews use a cluster#
Cluster membership is one signal Proofline uses to find related repositories for a pull request review. Related repositories must be in the same organization and GitHub installation. Selection depends on available catalogs of the interfaces repositories provide and consume, repository access, and the organization's Read related repositories setting. Cluster membership does not mean every member will be read.
For each selected repository, Proofline resolves its default branch once, records the exact commit, and reads only that commit. Related code helps explain the change. A default-branch commit does not establish which revision is deployed or prove a fact about the environment.
Related-repository reads are on by default. Only organization administrators can change the setting under Settings → Review policy → Code review → Read related repositories. Turning it off stops these reads.
Cluster changes affect later reviews. Earlier reviews retain the repositories and commits they recorded.