fix(ide): fix ide nudge setting

[skeshive]

Fix bug that resulted in IDE nudge being shown in every session due to writing incorrect setting

Linked Issues

Fixes #16990, #18684

[gemini-code-assist]

Summary of Changes

Hello @skeshive, 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 addresses a bug that caused the IDE integration nudge to reappear in every user session. The issue stemmed from an incorrect setting key being used to record the nudge's display status. By updating this key to the correct 'ide.hasSeenNudge' value, the system now accurately tracks when the nudge has been presented, ensuring it is shown only once as intended.

Highlights

• Corrected IDE Nudge Setting Key: The setting key used to record whether the IDE integration nudge has been seen was updated from 'hasSeenIdeIntegrationNudge' to 'ide.hasSeenNudge'.
• Prevented Repeated Nudge Display: This fix ensures that the IDE nudge is correctly marked as seen, preventing it from being displayed in every session.

Changelog

• packages/cli/src/ui/AppContainer.tsx
  • Updated the setting key for the IDE integration nudge to 'ide.hasSeenNudge' to correctly persist its seen status.

Activity

• No activity has been recorded for this pull request yet.

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. ↩

[github-actions]

Size Change: -102 B (0%)

Total Size: 23.9 MB

ℹ️ View Unchanged

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

[gemini-code-assist]

Code Review

This pull request addresses a bug where the IDE nudge was displayed in every session by correcting the setting key from hasSeenIdeIntegrationNudge to ide.hasSeenNudge, ensuring user preferences are correctly persisted. The updated code also maintains consistency across user selections. Regarding security, no vulnerabilities were found; however, the security audit could not be fully performed as all provided files were empty, preventing a comprehensive review.