Remove experimental note in extension settings docs

[chrstnb]

Summary

Details

Related Issues

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 @chrstnb, 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 updates the documentation for extension settings by removing a previously included note that labeled the feature as experimental. This change reflects the feature's maturity and readiness for general use by extension authors, providing clearer guidance without the prior cautionary warning.

Highlights

• Documentation Update: Removed the 'experimental feature' note from the extension settings documentation, indicating that extension settings are now considered stable and recommended for use.

Changelog

• docs/extensions/reference.md
  • Removed the 'experimental feature' warning from the settings section.

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 removes the 'experimental' note for extension settings from the documentation. While this is a good step towards stabilizing the feature, the change is incomplete. The underlying code still treats extension settings as experimental, guarded by an experimental.extensionConfig flag. This discrepancy between documentation and behavior can lead to user confusion. I've added a comment recommending that the related experimental checks and configuration be removed from the codebase to fully reflect the feature's stable status.

I am having trouble creating individual review comments. Click here to see my feedback.

docs/extensions/reference.md (182-184)

Removing the 'experimental' note implies this feature is now stable. However, the codebase still treats extension settings as an experimental feature, controlled by the experimental.extensionConfig flag. This inconsistency between the documentation and the application's behavior can be confusing for users.

For this feature to be considered stable, the corresponding experimental checks should also be removed from the code. For instance, the config command in packages/cli/src/commands/extensions/configure.ts still has a check for this flag:

if (!(settings.experimental?.extensionConfig ?? true)) {
  coreEvents.emitFeedback(
    'error',
    'Extension configuration is currently disabled. Enable it by setting "experimental.extensionConfig" to true.',
  );
  await exitCli();
  return;
}

To complete this change, please consider also removing this check and moving the extensionConfig setting out of the experimental section in schemas/settings.schema.json.

[github-actions]

Size Change: -2 B (0%)

Total Size: 24.3 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	24.3 MB	-2 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}