Add the ability to @ mention the gemini robot.#26207
Conversation
|
Size Change: -4 B (0%) Total Size: 33.9 MB
ℹ️ View Unchanged
|
Summary of ChangesHello, 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 enables interactive capabilities for the gemini-cli-robot, allowing it to respond to direct mentions from repository maintainers. The changes include new operational guidelines for handling interactive requests, updated security policies to ensure safe interactions, and a refactoring of existing documentation to maintain consistency across the bot's operational phases. Highlights
Ignored Files
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. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request centralizes repository policies, security protocols, and memory management into a new common.md file, while introducing an interactive.md phase for handling user-initiated requests. It also refactors the metrics.md documentation to reduce redundancy and streamline the investigation workflow. Review feedback identifies two necessary improvements: adding issue-comment.md to the list of files excluded from git staging to prevent transient artifacts from being committed, and relaxing the metrics output constraints to support existing JSON-based reporting formats.
Note: Security Review has been skipped due to the limited scope of the PR.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…-a' into gundermanc/repo-q-n-a
…i-cli#26208+26207 - BerriAI/litellm#26793 feat(proxy): durable agent workflow run tracking (needs-discussion — sequence-number race + missing tenancy scoping + Prisma error leak) - google-gemini/gemini-cli#26208 fix: suppress duplicate extension warnings (merge-after-nits) - google-gemini/gemini-cli#26207 Add @ mention the gemini robot (request-changes — critique-semantics flip + comment-step if guard regression + PAT scope concern)
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>
Summary
Adds the ability to @ mention the gemini-cli-robot, triggering the repo's resident agent for doing investigations, tasks, tracking new repository metrics, or implementing automation.
For security purposes: