docs: add terminal restart note to post-installation steps#59
Conversation
Users installing from an IDE (VS Code, Cursor) may not see changes immediately without restarting their terminal or IDE. Closes #44
Summary of ChangesHello @chicham, 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 improves the clarity of the post-installation process by adding a critical step to the documentation. It guides users on how to properly finalize their setup, ensuring that all configuration changes are applied correctly, particularly for those using integrated development environments. Highlights
🧠 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. Changelog
Activity
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 adds a helpful post-installation step to the README, reminding users to restart their terminal or IDE. This is a useful clarification, especially for users of integrated terminals. I've suggested a minor formatting change to add emphasis to a key instruction, which should help prevent user confusion.
|
|
||
| ### 4. Restart your terminal or IDE | ||
|
|
||
| Restart your terminal (or fully quit and reopen your IDE if using VS Code, Cursor, etc.) for all changes to take effect. |
There was a problem hiding this comment.
To better guide users and prevent a common point of confusion, consider adding emphasis to the action required for IDEs. Highlighting fully quit and reopen will draw attention to the fact that simply closing a terminal tab is often not enough.
| Restart your terminal (or fully quit and reopen your IDE if using VS Code, Cursor, etc.) for all changes to take effect. | |
| Restart your terminal (or **fully quit and reopen** your IDE if using VS Code, Cursor, etc.) for all changes to take effect. |
Summary
Adds a short step 4 to the Post-Installation section reminding users to restart their terminal or IDE after installation.
Users installing from VS Code, Cursor, or other IDEs may not see the dotfiles changes take effect until they fully restart, which can be confusing.
Closes #44