Update from support feedback: private repo missing on second deployment - #7052
Merged
Conversation
…oyment onboarding
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a help center article documenting the
?private=truere-authorize URL used when a private GitHub repo doesn't appear in the onboarding repo picker for a second Mintlify deployment. Support has had to share this internal URL manually because the initial GitHub authorization only requests thepublic_reposcope, so returning to onboarding reuses that authorization and never prompts for private-repo access.Changes
help-center/private-repo-missing-when-creating-second-deployment.mdxwith the symptom, thehttps://app.mintlify.com/api/onboarding/github/authorize?private=trueURL, follow-up steps for the GitHub App repository access list, and a link back todeploy/githubfor a full connection reset.docs.json.Support context
Note
Low Risk
Documentation-only Help center content and nav entries; no product or auth-code changes.
Overview
Adds a Help center article for when a private GitHub repo does not appear in the onboarding picker while creating a second Mintlify deployment from the same repo.
The article explains that the first GitHub auth only grants
public_repoand is reused on later onboarding, then documents the?private=truere-authorize URL, GitHub App repository-access follow-up, and a link to GitHub App connection issues. The page is registered in EN, ES, FR, and ZH nav.Reviewed by Cursor Bugbot for commit 457f7b1. Bugbot is set up for automated code reviews on this repo. Configure here.