fix(patch): cherry-pick d86b1f7 to release/v0.28.0-preview.2-pr-18447 to patch version v0.28.0-preview.2 and create version 0.28.0-preview.3

[gemini-cli-robot]

This PR automatically cherry-picks commit d86b1f7 to patch version v0.28.0-preview.2 in the preview release to create version 0.28.0-preview.3.

[gemini-code-assist]

Summary of Changes

Hello @gemini-cli-robot, 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 is an automated cherry-pick operation designed to patch version v0.28.0-preview.2, resulting in the creation of v0.28.0-preview.3. The primary objective of this patch is to enable the experimental.extensionConfig setting by default, which streamlines the process of requesting and fetching extension settings.

Highlights

• Configuration Default Change: The default value for the experimental.extensionConfig setting has been changed from false to true.
• Documentation Update: The documentation in docs/get-started/configuration.md has been updated to reflect the new default value for experimental.extensionConfig.
• Internal Schema Adjustment: The internal settings schema in packages/cli/src/config/settingsSchema.ts was modified to set the default for experimental.extensionConfig to true.
• JSON Schema Synchronization: The public JSON schema (schemas/settings.schema.json) has been updated to align with the new default value of true for extensionConfig.

Changelog

• docs/get-started/configuration.md
  • Updated the documented default value for experimental.extensionConfig to true.
• packages/cli/src/config/settingsSchema.ts
  • Modified the internal settings schema to set the default for experimental.extensionConfig to true.
• schemas/settings.schema.json
  • Updated the JSON schema to reflect the new default value of true for extensionConfig.

Activity

• This pull request was automatically generated by gemini-cli-robot to cherry-pick commit d86b1f7 for a patch release.
• No human activity has been recorded 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 cherry-picks a commit to change the default value of the experimental.extensionConfig setting from false to true. The change is consistently applied across the settings schema source file, the generated JSON schema, and the configuration documentation. The update is straightforward and appears correct, enabling this experimental feature by default.

[github-actions]

Size Change: -3 B (0%)

Total Size: 23.7 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.7 MB	-3 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}