docs(ovcli.conf): note interactive setup-cli + multi-server switch from #1916#1961
Merged
ZaynJarvis merged 2 commits intoMay 10, 2026
Merged
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
ZaynJarvis
pushed a commit
that referenced
this pull request
May 13, 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
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.
Problem
#1916 (
feat: ov CLI support, MaojiaSheng → ZaynJarvis 2026-05-08) addedov config setup-cli(interactiveovcli.confgeneration) andov config switch(multi-server profile switching). The PR updatedREADME.md(line 507) andREADME_CN.md(line 435) under "CLI/Client Configuration Examples", but the dedicatedovcli.confreference section in the configuration guide (docs/{en,zh}/guides/01-configuration.md) still only describes the manual JSON edit path. Users who reach the reference doc — typically the audience reading config field tables — never learn that the file can also be generated and swapped via the CLI.Fix
Adds one sentence at the top of each
### ovcli.confsubsection (EN + ZH), naming both subcommands and framing them as the manual-vs-interactive complement of editing by hand. Wording is grounded in #1916's own README diff —ov config setup-clifor interactive initialization,ov config switchfor switching between configurations. No new fields, no behavior change, no JSON example changes.Diff
docs/en/guides/01-configuration.md(+2):docs/zh/guides/01-configuration.md(+2): byte-for-byte semantic mirror in CN.Why this isn't redundant with the README catch in #1916
The README block lives under the onboarding "CLI/Client Configuration Examples" subsection — quickstart audience.
docs/{en,zh}/guides/01-configuration.mdis the dedicated reference doc covering the full ovcli.conf field table, CLI flag overrides, and gitignore behavior. Reference-doc readers do not necessarily read README first; surfacing the same two commands at the top of the dedicated section closes the discoverability gap without duplicating implementation detail.Source PR & precedent
temp_uploadserver config +ovcli.conf upload.modedrift from feat(server): add shared temp upload mode #1899 in the same file.