Optimize Direct review and flatten knowledge routes - #33
Merged
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
What changed
knowledge/_archive/andknowledge/遗言/contentguides/layers under source ownersWhy
Direct reviews were accurate but spent too much time navigating knowledge and repeating searches. The knowledge tree also forced readers through mechanical
guides/_index.mdhops before reaching a concrete feature page.Strict compatibility is preserved: its fixed briefing files remain unchanged, and recursive
doc_search/doc_readnow resolve the flatter paths directly.Validation
doc_search("并行策略")resolvescomponents/diffusion/parallelism.mdgit diff --checkpassedRefs #24