[Follow Up Questions] Re-enable follow up questions module

[gmechali]

This is a safe move as we know our current quota can handle our current user load.
We had to disable it previously due to an incident where hyperlinks gave crawlers far more explore pages to crawl.
If we have a very high user spike, we can easily turn off this feature temporarily. We have discussed a more permanent fix to address the possibility of using too much Gemini quota.

[gemini-code-assist]

Summary of Changes

Hello @gmechali, 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 focuses on reactivating the 'follow up questions' module by enabling its corresponding feature flag. The decision to re-enable comes after assessing the system's capacity to handle the current user load, addressing previous concerns related to excessive crawling. While a temporary disablement mechanism is in place for potential user spikes, a long-term solution for managing Gemini quota usage is being actively explored.

Highlights

• Feature Re-enablement: The follow_up_questions_ga feature flag has been re-enabled, allowing the 'follow up questions' module to become active again.
• Safety and Quota Management: This re-enablement is deemed safe as the current system quota can handle the user load. A temporary disablement option is available for user spikes, and a permanent solution for Gemini quota management is under discussion.
• Previous Disablement Reason: The feature was previously disabled due to an incident where hyperlinks led crawlers to explore an excessive number of pages.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 re-enables the follow_up_questions_ga feature flag. While the change is simple, it re-introduces a known risk. My review highlights that enabling this feature without first implementing a fix for the web crawler issue (which caused a previous incident) could lead to Gemini quota exhaustion. I have added a high-severity comment on the configuration change, recommending that the underlying issue be addressed before deploying this change to production.

[gemini-code-assist]

Enabling this feature flag re-introduces a risk that led to a previous incident. The feature generates hyperlinks that web crawlers can follow, potentially causing excessive calls to the Gemini API and exhausting your quota.

The pull request description mentions that a more permanent fix has been discussed. To prevent a recurrence of the incident, it is strongly recommended to implement this fix before enabling the feature in production. A robust solution would be to add a rel=\"nofollow\" attribute to the generated <a> tags in static/js/apps/explore/follow_up_questions.tsx to instruct crawlers not to follow these links.