Connections and repositories
A source connection lets Signals Corps discover repositories. Supply Chain monitors a repository only when the Workspace’s plan and repository selection allow it.
Connection state
Section titled “Connection state”The GitHub App connection can be:
- Not configured: the Workspace has no active GitHub installation.
- Connected: Signals Corps can receive events for the installation and inspect the repositories GitHub makes available.
- Degraded: the installation exists, but access or delivery needs attention.
Connecting GitHub does not make repository source public. Installation credentials stay on the server and never enter the browser or The Captain.
Repository access and monitoring
Section titled “Repository access and monitoring”GitHub controls which repositories the installation can access. Signals Corps records each accessible repository inside one Workspace.
Repository access and monitoring are separate:
- Accessible means the GitHub installation can read the repository.
- Selected means a Workspace owner or administrator chose the repository for continuous monitoring.
- Monitored means current policy and plan capacity allow Supply Chain to scan new revisions.
- Not monitored means Supply Chain retains allowed history but does not start new continuous scans for that repository.
Public repositories can be monitored under the Free plan. Private and internal repositories use the Workspace’s paid repository capacity. Reaching the limit blocks another assignment; it does not create an automatic overage charge.