documentiong ensures ripgrep

[Jatin24062005]

Summary

This PR documents the current ripgrep selection behavior in Gemini CLI.

The CLI intentionally uses a managed ripgrep binary and does not yet prefer a system-installed rg, pending checksum verification and internalization of get-ripgrep.

No runtime behavior is changed.

Related Issues

#11438

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 enhances the clarity of the Gemini CLI's ripgrep binary management by adding detailed documentation. It explains the current strategy of preferring a managed ripgrep binary and the reasons for not utilizing system-installed versions, without altering any existing operational logic. The primary goal is to provide transparency regarding the ripgrep selection mechanism for developers.

Highlights

• Documentation: Added comprehensive JSDoc comments to the ensureRipgrepAvailable function, clarifying the current ripgrep binary selection behavior within the Gemini CLI.
• Behavior Clarification: Explicitly documented that the CLI intentionally prefers a managed ripgrep binary over system-installed versions, outlining the technical reasons and dependencies blocking a change to prefer system-installed rg.
• No Functional Change: Confirmed that this pull request introduces no changes to the runtime behavior or functionality of the ripgrep acquisition process.

Changelog

• packages/core/src/tools/ripGrep.ts
  • Added JSDoc comments to the ensureRipgrepAvailable function to document the ripgrep binary selection logic.

Activity

• No human activity has occurred on this pull request yet.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds documentation to the ensureRipgrepAvailable function, clarifying the behavior of ripgrep binary selection. The new comment correctly states that the CLI prefers a managed binary over a system-installed one and explains the rationale. The change is purely documentary and introduces no runtime modifications. The PR title contains a typo ('documentiong') and does not adhere to the Conventional Commits standard specified in the repository's style guide; it could be improved to docs(core): document ripgrep selection behavior.

[chinovelez022-ctrl]

CHINO G.F.M. El vie, 6 de mar de 2026, 12:24 a. m., Gaurav ***@***.***> escribió:

…

Merged #21298 <#21298> into main. — Reply to this email directly, view it on GitHub <#21298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BU6RRMEIAZRGG6JXQJPVUST4PJVI5AVCNFSM6AAAAACWITMD6CVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRTGMZDEMZXHE2TGOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>