add feature flag for gemini 3.5 flash#6320
Conversation
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 introduces a new feature flag to facilitate the upcoming migration from Gemini 3 Flash to Gemini 3.5 Flash. By adding this flag to the configuration files, the team can safely toggle and test the new model version across various environments in preparation for the scheduled deprecation of the previous version. Highlights
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 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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces a new feature flag, enable_gemini_3_5_flash, which is disabled by default across multiple environment configuration files (autopush, custom, dev, local, and staging). This flag is intended to enable Gemini 3.5 Flash for NL detection. There are no review comments, so I have no additional feedback to provide.
Gemini is planning to deprecate Gemini 3 flash preview in June 15th, this change is bumping up flash to 3.5, this change add feature flag for non prod to help bump up Gemini flash to 3.5