Update from support feedback: editor recovery after GitHub and repo changes#6429
Open
mintlify-development[bot] wants to merge 1 commit into
Open
Update from support feedback: editor recovery after GitHub and repo changes#6429mintlify-development[bot] wants to merge 1 commit into
mintlify-development[bot] wants to merge 1 commit into
Conversation
…, and Slack after repo switch
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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 troubleshooting coverage for web editor states that repeatedly stumped users after GitHub App or connected-repository changes.
Changes
editor/branching-and-publishing.mdx: new Troubleshooting section covering the GitHub connect prompt blocking the editor, transient 502s on publish menu actions, missing preview deployments for pull requests from forks, and Slack notifications going silent after switching the connected repository.deploy/github.mdx: note under Configure docs source that switching the connected repository requires reinstalling the Slack app and reselecting automation notification channels.deploy/preview-deployments.mdx: add fork pull requests to the preview troubleshooting list, with the recommended workaround.Context
Recent support conversations showed users getting stuck in states not covered by the existing editor and GitHub docs, including editors becoming unusable after a GitHub reconnect prompt, 502s when accepting a PR from the editor, silent Slack notifications after switching repos, and expecting previews to build from fork branches.
Note
Low Risk
Documentation-only updates with no application, auth, or data-handling code changes.
Overview
Adds troubleshooting aimed at support pain points after GitHub App or connected-repository changes.
editor/branching-and-publishing.mdxgets a new Troubleshooting section: recovering when the editor sticks on Connect GitHub (reinstall app, confirm repo access, reload), handling transient 502 errors on merge/approve/PR actions from the publish menu, why fork PRs don’t get previews and upstream/manual-preview workarounds, and reconnecting Slack after a docs source switch.deploy/github.mdxadds a Note under Configure docs source that switching the connected repo does not migrate the Slack agent or automation notification channels.deploy/preview-deployments.mdxadds a troubleshooting bullet for pull requests from forks, with the same upstream-branch or manual-preview guidance.Reviewed by Cursor Bugbot for commit f6b87a4. Bugbot is set up for automated code reviews on this repo. Configure here.