Skip to content

Remove vis tool feature flag from configs#6287

Merged
juliawu merged 1 commit into
datacommonsorg:masterfrom
juliawu:delete-vis-tool-feature-flag
May 13, 2026
Merged

Remove vis tool feature flag from configs#6287
juliawu merged 1 commit into
datacommonsorg:masterfrom
juliawu:delete-vis-tool-feature-flag

Conversation

@juliawu
Copy link
Copy Markdown
Contributor

@juliawu juliawu commented May 13, 2026

Removes the standardized_vis_tool feature flag from feature flag config .json files.

Context

All remaining code references to the standardized_vis_tool flag have been removed in #6240. That change has hit production in release v23.4.10 and custom DC stable release.

This change completes the deprecation by removing the now-unused feature flag from our feature flag configs.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 completes the deprecation process for the 'standardized_vis_tool' feature. Following the removal of all code references to this flag in a previous change, this PR cleans up the remaining configuration entries across all environments to ensure a consistent and clutter-free codebase.

Highlights

  • Feature Flag Cleanup: Removed the 'standardized_vis_tool' feature flag from all environment-specific configuration files.
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes the "standardized_vis_tool" feature flag from all environment configuration files, including autopush, custom, dev, local, production, and staging. I have no feedback to provide as there are no review comments.

@juliawu juliawu marked this pull request as ready for review May 13, 2026 21:16
@juliawu juliawu requested review from beets and gmechali May 13, 2026 21:16
@juliawu juliawu merged commit 317683d into datacommonsorg:master May 13, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants