Skip to content

Fix typo in A2A EXPERIMENTAL warning#4462

Open
ftnext wants to merge 2 commits intogoogle:mainfrom
ftnext:fix-typo-a2a-experimental-warning
Open

Fix typo in A2A EXPERIMENTAL warning#4462
ftnext wants to merge 2 commits intogoogle:mainfrom
ftnext:fix-typo-a2a-experimental-warning

Conversation

@ftnext
Copy link
Contributor

@ftnext ftnext commented Feb 12, 2026

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

2. Or, if no issue exists, describe the change:

Problem:
I found a typo: arethemselves

/.../adk-python/src/google/adk/a2a/converters/event_converter.py:245: UserWarning: [EXPERIMENTAL] convert_a2a_message_to_event: ADK Implementation for A2A support (A2aAgentExecutor, RemoteA2aAgent and corresponding supporting components etc.) is in experimental mode and is subjected to breaking changes. A2A protocol and SDK arethemselves not experimental. Once it's stable enough the experimental mode will be removed. Your feedback is welcome.

Solution:
Just fix

Testing Plan

This is typo fix

Unit Tests:

N/A

Manual End-to-End (E2E) Tests:

N/A

Checklist

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have manually tested my changes end-to-end.
  • Any dependent changes have been merged and published in downstream modules.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ftnext, 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 addresses a minor but important textual correction within the A2A experimental warning message. The change ensures the warning is grammatically correct and improves readability, without altering any functional aspects of the code.

Highlights

  • Typo Fix: Corrected a grammatical error in the experimental warning message within the A2A module, specifically adding a space between 'are' and 'themselves'.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/google/adk/a2a/experimental.py
    • Corrected a typo in the default_message string, adding a space between 'are' and 'themselves'.
Activity
  • The author identified a typo in an experimental warning message.
  • The author created this pull request to fix the identified typo.
  • The author indicated that unit and end-to-end tests were not applicable for this typo fix.
  • The author completed a self-review and confirmed reading the contribution guide.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes a typo in the A2A experimental feature warning message. I've added one suggestion to further improve the grammar of the same message for better clarity.

@adk-bot adk-bot added the documentation [Component] This issue is related to documentation, it will be transferred to adk-docs label Feb 12, 2026
@ryanaiagent ryanaiagent self-assigned this Feb 13, 2026
@ryanaiagent
Copy link
Collaborator

Hi @ftnext ,Thank you for your contribution! We appreciate you taking the time to submit this pull request. Can you also apply the suggestion.

@ryanaiagent ryanaiagent added the request clarification [Status] The maintainer need clarification or more information from the author label Feb 13, 2026
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@ftnext
Copy link
Contributor Author

ftnext commented Feb 13, 2026

@ryanaiagent Thanks for your comment! I applied Gemini's suggestion.

@sasha-gitg sasha-gitg assigned sasha-gitg and unassigned ryanaiagent Feb 13, 2026
@sasha-gitg sasha-gitg removed the request clarification [Status] The maintainer need clarification or more information from the author label Feb 13, 2026
@sasha-gitg sasha-gitg added the ready to pull [Status] This PR is ready to be importing back to Google label Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation [Component] This issue is related to documentation, it will be transferred to adk-docs ready to pull [Status] This PR is ready to be importing back to Google

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants