test: sync mypy command in GEMINI.md with CI#733
Conversation
In [CI](https://github.com/a2aproject/a2a-python/blob/3ad2503107dd1faa71ab6b56da9017141e24e34c/.github/workflows/linter.yaml#L41) we don't run mypy on tests, so in order to prevent model from encountering old issues specify the same command as in CI.
Summary of ChangesHello @ishymko, 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 synchronizes the Highlights
Changelog
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 updates the mypy command in GEMINI.md to uv run mypy src, aligning it with the project's CI configuration. This change correctly scopes type checking to the src directory, which is consistent with other tool configurations like pyright. The update improves consistency between the local development environment and CI, and the documentation change is clear and correct.
Branch protection rule check failed
In CI we don't run mypy on tests, so in order to prevent model from encountering old issues specify the same command as in CI.