Update from support feedback: editor branch list visibility rule - #7171
Merged
Merged
Conversation
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. |
The visibility rule as first written covered only branches pushed directly to a Git provider. Verified against the editor branch code: records are also soft-deleted when a pull request is merged or closed (editorBranch.service.ts), the list defaults to PR states none/draft/open (editorBranch.validators.ts), and cross-repository (fork) pull requests are filtered out. Those cases match the support threads about branches disappearing after publishing, so document them. Also scope the URL workaround: without an editor branch record, autocommit is skipped, the branch diff fails, and rename/delete return 404. It is a view-and-edit fallback, not an equivalent to opening a pull request. Drop the hand-written es/fr/zh pages and locale nav entries; those are generated after merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ethanpalm
reviewed
Aug 31, 2026
ethanpalm
approved these changes
Aug 31, 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
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
Documents that the web editor branch dropdown intentionally lists only branches created in the editor or branches with an open PR/MR targeting the deployment branch. Several users this week believed branches pushed directly to GitHub/GitLab were deleted when they stopped appearing in the dropdown. Adds the rule and both workarounds (open a PR/MR, or swap the branch name in the editor URL) to the branches guide, plus a help center article for the "my branch disappeared" symptom.
Changes
guides/branches.mdx: state the branch dropdown visibility rule and workarounds in the "Switch branches" sectionhelp-center/branch-missing-from-editor-branch-list.mdx: new article covering the symptom, the rule, and both workaroundsdocs.json: register the new help center pageSupport context
Note
Low Risk
Documentation-only changes with no impact on product behavior, auth, or data handling.
Overview
Documents why repo branches can be missing from the web editor branch dropdown and how users can still work on them, addressing support cases where teams thought branches were deleted.
Adds a new help center article that explains the dropdown only shows editor-created branches (without merged/closed PRs) and branches with an open PR/MR targeting the deployment branch, plus exclusions (direct Git pushes, merged/closed PRs, wrong target branch, fork PRs). It covers workarounds: open a same-repo PR for full editor support, or change the branch segment in the editor URL with limited functionality until a PR exists.
The Work with branches guide’s “Switch branches” web editor section now states the same visibility rule and links to the help article.
docs.jsonregisters the new help center page in navigation.Reviewed by Cursor Bugbot for commit 47cf596. Bugbot is set up for automated code reviews on this repo. Configure here.