[v0.9.1-dev][doc] Correct the doc in v0.9.1-dev #4965
Merged
Conversation
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
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request primarily focuses on updating the documentation structure. It removes several old documentation files related to model adding and moves/renames a tutorial document to a new feature guide section. The title of the moved document was also slightly adjusted for broader applicability. No critical or high-severity issues were identified in these documentation changes.
Collaborator
|
please fix the CI |
lilinsiman
force-pushed
the
091_info
branch
2 times, most recently
from
4f9d480 to
3c4f056
Compare
Signed-off-by: lilinsiman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 this PR does / why we need it?
Correct the doc in v0.9.1-dev
Does this PR introduce any user-facing change?
no
How was this patch tested?
ut