Repositories

Choose what to bring into the workspacePermalink to Choose what to bring into the workspace

Repositories is the working list for the current Relane workspace. A provider can authorize access to more repositories than you choose to import. Use Connect repository to open the connection panel and select the account or installation that can see the code you want.

• GitHub: select the linked installation, then use Bind beside a granted repository. Bound confirms the import.
• GitLab Cloud and Bitbucket Cloud: choose See repositories beside the connected account and use Add. Added confirms the import.
• Review the full repository name and default branch. A provider's Archived label describes the source repository; check the imported repository's own state and scan eligibility in Relane before scanning.
• A successful import makes the repository available in Repositories and Start a scan. It does not automatically start a scan.

Read repository statesPermalink to Read repository states

Connection health and repository state answer different questions. Connected describes an account authorization; Active describes an imported repository. Neither an old access check nor a previously successful scan guarantees that the provider still grants access now. Check both when a new scan cannot read the repository.

Disconnect, reconnect, and re-addPermalink to Disconnect, reconnect, and re-add

Disconnect on a repository card archives that repository in Relane and removes it from scanning. The confirmation explains this before you proceed. It does not delete the repository at your source-control provider. If a scan is in progress, let it finish or cancel it before disconnecting.

An archived repository returns through Connect repository: use Bind for GitHub or Add for GitLab and Bitbucket. Re-adding the same repository in the same workspace retains its previous scans and findings. Use History on its card to review earlier scans.

For a disconnected or suspended GitHub repository, Reconnect checks the installation's access again. Restore permissions on GitHub first; a completed reconnect attempt is not proof of restored access. For GitLab and Bitbucket authorization problems, renew the provider connection and Add the repository through that connection instead.

Disconnect beside an account in Where your code lives has a broader effect: Relane loses access through that connection for every repository using it. Review the confirmation carefully. Restoring that access requires browser authorization again. If you also want to remove the application's grant at the provider, manage that separately in the provider's account settings.

Check readiness before scanningPermalink to Check readiness before scanning

Open Start a scan to choose an eligible imported repository. Repositories that cannot be scanned are disabled with a reason. Review Branch or ref rather than assuming every repository uses the same default branch, then choose Start scan.

• The repository is missing: confirm the Relane workspace and that import finished with Bound or Added, then reopen Repositories.
• The scan action is disabled: follow the displayed access or archive reason. For a provider authorization problem, check the connection as well as the repository card.
• A scan is already running: open it from Scans instead of repeatedly trying to start another.
• The scan reports a repository access error: verify that the connected provider account can still read the repository, restore or renew access, and retry with a valid branch or ref.
• Scanning is temporarily unavailable: follow the console's retry guidance. Changing provider permissions will not resolve a scanning-service availability message.