docs: cross-reference the standalone dsh-plugin for DSH-only users - #270
Open
ralf0131 wants to merge 1 commit into
Open
docs: cross-reference the standalone dsh-plugin for DSH-only users#270ralf0131 wants to merge 1 commit into
ralf0131 wants to merge 1 commit into
Conversation
Readers who only use DeepSeek Harness and already run an OTLP backend do not need a local collector. Point them at loongsuite/dsh-plugin and spell out how the two paths differ (multi-agent collection and fan-out here, in-process direct OTLP export there). Change-Id: I335006f402ec694a9cc3b1dbfefd1a45c1e391e5 Co-developed-by: Qoder <noreply@qoder.com>
There was a problem hiding this comment.
Pull request overview
This PR improves onboarding documentation by cross-referencing the standalone @loongsuite/dsh-plugin as the lighter-weight option for DeepSeek Harness (DSH)-only users who already have an OTLP backend, reducing unnecessary Pilot installs.
Changes:
- Add a short “DSH-only vs Pilot” guidance block in
README.mdunder the DeepSeek Harness integration section. - Add the equivalent cross-reference and explanation in
README.zh-CN.md, keeping wording aligned between the two READMEs.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Adds a DSH-only pointer to @loongsuite/dsh-plugin and clarifies when to choose Pilot vs the standalone plugin. |
| README.zh-CN.md | Adds the same DSH-only pointer and Pilot-vs-plugin distinction in Chinese under the DSH integration section. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Both READMEs now mention @loongsuite/dsh-plugin right below the DeepSeek Harness integration paragraph, and spell out how the two paths differ:
Readers who only use DSH and already run an OTLP backend currently land here and install a collector they do not need; the cross-reference sends them to the lighter option. Wording kept symmetric with the comparison table in the dsh-plugin README.