Skip to main content
When you create a second Mintlify deployment from the same private GitHub repository that already backs an existing deployment, the onboarding repo picker may not list that private repository. This happens because your initial GitHub authorization only granted the public_repo scope, and returning to onboarding reuses the existing authorization instead of prompting for private access again. You can create separate deployments from the same repository. Mintlify does not require a new repository per deployment. For combining multiple repositories into one site, see Multi-repo setup instead.

​
Re-authorize with private-repo access

Visit this URL while signed in to the Mintlify dashboard:
The ?private=true query parameter requests the GitHub repo scope, which grants access to private repositories. GitHub prompts you to authorize the additional scope, then returns you to the dashboard. After re-authorizing:
  1. Return to the onboarding flow for your new deployment.
  2. Reopen the repository picker. Your private repository is now selectable.
  3. Continue onboarding to finish creating the second deployment.

​
If the repository still doesn’t appear

If the picker still doesn’t list the repository after re-authorizing, the Mintlify GitHub App installation on that repository’s organization may need to be updated to include it:
  1. Open your GitHub App settings and select the organization that owns the repository.
  2. Under Repository access, either select All repositories or add the specific repository under Only select repositories.
  3. Save the change and reopen the repo picker.
For a full reset of the GitHub App connection, see GitHub App connection issues.

Related topics

GitHubDeploymentsGitLab