Check which repository connection prevented a companion read

If an expected companion was skipped, open the environment assessment’s Configuration and preferences → Companion repositories → Repositories and find its recorded reason.

Match the issue to its owner#

A repository without a stable GitHub identity differs from one that was no longer linked behind the connected installation. Check the organization’s repository list and the installation’s repository selection for the latter. A membership-withdrawn reason instead points to the repository cluster.

If the primary reviewed repository was no longer readable, start with that repository. Correcting a connection or cluster helps later work. The completed assessment still records the reason that applied to its read.

Search help

Tab to a result. Enter to open. Escape to close.