Repository navigation
Rewrite GHES setup around the dashboard GitHub Enterprise flow - #8049
Draft
brandonmcconnell wants to merge 1 commit into
Draft
brandonmcconnell wants to merge 1 commit into
brandonmcconnell wants to merge 1 commit into
Conversation
Co-authored-by: brandon <brandon@dreamthinkbuild.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This branch was successfully deployed
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.
Documentation changes
Rewrites
deploy/ghes.mdxaround the new self-serve GitHub Enterprise flow in Git settings (spec). Customers enter their GHES host and organization, create an organization-owned GitHub App from a manifest, and install it. Nobody downloads a.pemor sends credentials to Mintlify.Keep this in draft until mintlify/mint#13636 and mintlify/server#9782 ship.
For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience