docs: JS toolbox-adk sdk doc migration#2395
Conversation
Summary of ChangesHello @rapid-killer-9, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request migrates and introduces new, detailed documentation for the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request adds a new markdown document for the Toolbox-adk SDK, providing documentation and usage examples. The review focuses on ensuring the documentation is clear, correct, and follows best practices for SDK usage. No specific style guide was provided, so the review defaults to general documentation best practices.
Updated title and description for the adk documentation.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
Can you ensure that the core readme is consistent with these changes? I just wrote a PR: googleapis/mcp-toolbox-sdk-js#262 Similarly, please raise PRs to update model name etc. |
I’ve confirmed that the variable names in the JS PR are already consistent, as this was handled previously. I have now also added a note regarding model deprecation to ensure everything is aligned. |
|
Please fix the link check |
664e486 to
779535a
Compare
This PR migrates the @toolbox-sdk/adk JavaScript SDK documentation to the main documentation site. It ensures all technical guides and references are centralized and up-to-date with the latest project standards.
Key Changes
Documentation Migration: Ported content from the JS SDK repository to the main docsite.
Compatibility Updates: Updated the documentation to support the current Hugo version used by the site.
Model Update: Updated all Gemini model references to Gemini 3 Preview to align with the latest SDK capabilities.
Content Enhancement: Refined setup guides, authentication sections, and ADK integration examples for better readability.