test: add help article on repo visibility changes - #7498
Closed
mintlify[bot] wants to merge 2 commits into
Closed
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
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.
Summary
Adds a public help center article for Git-dependent features that break after a repository changes between private and public.
Changes
help-center/features-stop-working-after-changing-repository-visibility.mdxcovering symptoms, expected behavior for each visibility direction, and the Git settings revalidation shortcut.docs.json.es/,fr/, andzh/, and added it toes.json,fr.json, andzh.json.Context
This guidance existed only in the internal
git-revalidationassistant skill, so the published docs didn't cover it.Note
Low Risk
Documentation and navigation updates only; no application or infrastructure code changes.
Overview
Adds a new Help center article explaining why edit suggestions, preview deployments, and branch options can break after a docs repo switches between public and private, and how to fix it by revalidating the Git connection (dashboard shortcut and GitLab Active badge).
The article is published in English, Spanish, French, and Chinese, and each locale’s nav config (
docs.json,es.json,fr.json,zh.json) now listsfeatures-stop-working-after-changing-repository-visibilityin the Help center group. It also clarifies that private → public revalidation restores feedback features, while public → private hides them by design but still fixes stale-connection symptoms.Reviewed by Cursor Bugbot for commit a77084f. Bugbot is set up for automated code reviews on this repo. Configure here.