Managing repository access
Repository access is managed on GitHub — Velumi reflects whatever the GitHub App installation permits. You can change the scope at any time without reinstalling.
Adding more repositories
From the Velumi dashboard:
Organization → Integrations → installation → Manage on GitHub
GitHub opens the installation settings. Under Repository access:
- Switch to All repositories to grant access to all current and future repos
- Or keep Only select repositories and add the new repo(s) to the list
Changes apply immediately. The new repos appear in Velumi's source picker as soon as you refresh.
Removing a repository
Same flow — open the installation on GitHub and either switch to a smaller selection or remove specific repos from the list.
Projects already deployed from a removed repo keep their last-built image running. New deployments will fail until access is restored.
Adding another installation
If you need to connect a second GitHub account or organization, go to Organization → Integrations → Add Another Installation and follow the same install flow. Each installation is listed separately.
This is also required if your project depends on private npm packages from a GitHub org that doesn't own the source repo. Velumi mints tokens for all installations on your Velumi org at deploy time, so adding the package org's installation makes those packages available during npm install / pnpm install. See Installing the GitHub App — Private npm packages.
Removing an entire installation
To disconnect a GitHub account or organization from Velumi:
- In Velumi: Organization → Integrations → installation → Remove
- In GitHub: Settings → Applications → Installed GitHub Apps → Velumi → Uninstall
Either side is sufficient. Projects that relied on the removed installation will stop being able to deploy new code until you reinstall.
Suspended installations
If an installation shows Suspended, GitHub has paused it. Open it on GitHub and unsuspend it — or remove and reinstall.