docs: reference suggest_pipeline tool status#397
Open
QuantumByte-01 wants to merge 2 commits intosktime:mainfrom
Open
docs: reference suggest_pipeline tool status#397QuantumByte-01 wants to merge 2 commits intosktime:mainfrom
QuantumByte-01 wants to merge 2 commits intosktime:mainfrom
Conversation
QuantumByte-01
force-pushed
the
docs/suggest-pipeline-docs
branch
from
05d9c4b to
6778406
Compare
QuantumByte-01
force-pushed
the
docs/suggest-pipeline-docs
branch
from
6778406 to
138bd2f
Compare
Keep upstream tool categories and retain suggest_pipeline cross-refs (sktime#288, sktime#301). Made-with: Cursor
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\n- Updates docs to mention the suggest_pipeline MCP tool, as proposed in #288 and implemented in #301.\n\n## Context\nIssue #288 was opened after noticing suggest_pipeline was listed as planned but not exposed. There is already an implementation PR (#301). This PR is a small docs follow-up so the code explanation page reflects the current status.\n\n## Related\n- #288\n- #301\n
Made with Cursor