[v0/v1 migration] Remove use_v2_api feature flag#6404
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 finalizes the migration to the V2 API by removing the 'use_v2_api' feature flag across all server environment configurations. This change follows previous efforts to clean up the codebase by eliminating obsolete flag references. 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
|
|
Hey Nick! The rule is never submit a change that includes production.json AND another file. Can you remove the change to production.json, submitt his PR with all the other files, then put up a separate PR just for production.json? |
Updated! Thank you for the sugggestion. In this case the separation has an additional benefit that we can do this merge now (we need to wait until production actually has 6355 before merging a change the prod flag). |
Related PRs
6355
6396
Description
Remove
use_v2_apifeature flag from all environment configurations.This is a follow-up to 6355 and 6396 (linked above) that removed all usage of those flags from the codebase.