chore : remove a redundant tip#14947
Conversation
Summary of ChangesHello @JayadityaGit, 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 streamlines the user interface by removing a specific tip from the application's constant tips list. The modification ensures that users receive only pertinent advice, thereby improving the clarity and efficiency of the user experience by eliminating redundant information. 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 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 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
|
There was a problem hiding this comment.
Code Review
This pull request removes a tip explaining that the 'Enter' key is used to submit prompts. The rationale is that this tip is redundant. However, this change could negatively impact new users by making a fundamental action less discoverable. The 'Enter' key also accepts suggestions, which could cause confusion. For this reason, I have recommended reverting this change to ensure a smooth onboarding experience for all users.
| 'Navigate your prompt history with the Up and Down arrows...', | ||
| 'You can also use Ctrl+P (up) and Ctrl+N (down) for history...', | ||
| 'Search through command history with Ctrl+R...', | ||
| 'Submit your prompt to Gemini with Enter...', |
There was a problem hiding this comment.
Removing this tip harms the discoverability of the primary submission action for new users. While 'Enter' is a common convention, its dual role for accepting suggestions (as mentioned in another tip: 'Accept an autocomplete suggestion with Tab or Enter...') can create confusion. Explicitly stating how to submit the prompt is important for a smooth onboarding experience. Reverting this change is recommended to avoid a potential usability regression.
There was a problem hiding this comment.
Since the cycler can only be activated after the user already has discovered about this, logically it does not make any sense to keep this tip 😅
came across these errors in the GitHub CI/CD logs, though they don’t appear to be caused by my changes. |


Summary
Since the phrase cycler can only be activated after the user has given input and pressed enter, I feel this tip is redundant.
Pre-Merge Checklist