Reference / 3 MIN READ

Connect GitHub

List accessible repositories using a local CLI session or a private per-user token.

Local connection

Sign in with GitHub CLI on the machine running Papliba Local, then open GitHub and refresh. You can instead enter a personal access token in the page or configure PAPLIBA_GITHUB_TOKEN on the runner.

gh auth login

Hosted connection

Each hosted user supplies a separate personal access token. The server stores it encrypted within that user’s workspace. Hosted mode does not use the server owner’s GitHub CLI login or environment token. Stored credentials are not returned to the browser.

Permissions and results

Use the smallest token scope that provides access to the repositories you need. Fine-grained tokens need the appropriate repository read access. Classic tokens use repo access for private repositories; read:org can be needed to include organization repositories. Your organization may require token approval or SSO authorization.

The view lists repository names, visibility, languages, and update times. It does not fetch repository contents. Refresh reloads the list from GitHub.

Protect the stored credential

Local credentials use ASP.NET Data Protection and owner-only file permissions. Windows also protects keys with DPAPI. On macOS and Linux, key protection relies on filesystem permissions rather than Keychain. Hosted deployments require a private encryption certificate and protected persistent storage.