Repositories
Repository states, and what connect, disconnect, reconnect and archive each mean.
Repository statesPermalink to Repository states
Every connected repository is in exactly one of four states. Only Active repositories can be scanned; the console shows the reason and the next step for the others.
| State | What it means | Can it be scanned? |
|---|---|---|
| Active | Relane Security can read the repository and it is eligible for scanning. | Yes |
| Access suspended | The GitHub App installation is suspended, so the repository cannot be read. | No — restore access from GitHub |
| Disconnected | Access is no longer granted for this repository. | No — reconnect it to resume scanning |
| Archived | The repository was removed from scanning. | No — re-add it to scan |
Disconnect, reconnect and archivePermalink to Disconnect, reconnect and archive
Disconnecting a repository stops it being scanned and leaves its previous scans and findings readable. Reconnecting it restores eligibility; you do not lose scan history by disconnecting.
Archiving removes a repository from scanning. Its history remains, and re-adding the repository is what brings it back.
Where this happens in the console
History survives a disconnect
Why a repository cannot be scannedPermalink to Why a repository cannot be scanned
The scan button is unavailable for any repository that is not Active, and the console states the reason. The server enforces the same rule, so a scan cannot be started against an ineligible repository even if the page is stale.
| Reason | What to do |
|---|---|
| Disconnected | This repository was disconnected. Reconnect it to resume scanning. |
| Archived | This repository was removed from scanning. Re-add it to scan. |
| Access suspended | The GitHub App installation is suspended. Restore access to scan. |
| Unavailable | This repository is not available for scanning right now. |