docs: clarify GEMINI_CLI_HOME settings path

[vivekjm]

Summary

• Clarify that GEMINI_CLI_HOME points to the parent directory for user-level state
• Document that user settings should be placed at $GEMINI_CLI_HOME/.gemini/settings.json
• Add the same path guidance to the enterprise user isolation docs

Fixes #23622

Testing

• npm exec --yes prettier -- --check docs/reference/configuration.md docs/cli/enterprise.md

[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 improves the documentation for the GEMINI_CLI_HOME environment variable. By providing clearer path examples and explaining the directory structure, it helps users correctly configure their settings files in isolated or shared environments, resolving ambiguity regarding where the CLI expects configuration files to reside.

Highlights

• Documentation Clarification: Clarified that GEMINI_CLI_HOME serves as the parent directory for user-level state and that the CLI automatically creates a .gemini subdirectory.
• Settings Path Guidance: Added explicit instructions on where to place the settings.json file within the GEMINI_CLI_HOME structure for both Unix-like and Windows systems.

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 the 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 counterproductive. 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

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

[github-actions]

📊 PR Size: size/XS

• Lines changed: 7
• Additions: +6
• Deletions: -1
• Files changed: 2

[gemini-code-assist]

Code Review

This pull request updates the documentation in docs/cli/enterprise.md and docs/reference/configuration.md to clarify how the GEMINI_CLI_HOME environment variable affects the location of the user-level settings.json file. It specifies that settings are loaded from a .gemini subdirectory within the path defined by GEMINI_CLI_HOME, providing concrete examples for macOS/Linux and Windows. There are no review comments, and I have no feedback to provide.

_{Note: Security Review has been skipped due to the limited scope of the PR.}