docs: mention to run in powershell where needed in quickstart for Windows

[markstur]

Summary

Add missing mention of "Run in PowerShell" because the command with semi-colons fails on command-line.

Also tweaked the mention of interactive prompts because there are none. Saying "follow instructions" work for the printed HINTs about setup and would also work if it became interactive.

Linked Issues

Fixes #1927

Documentation

• No Docs Needed:

If this PR adds new feature or changes existing. Make sure documentation is adjusted accordingly. If the docs is not needed, please explain why.

[gemini-code-assist]

Summary of Changes

Hello @markstur, 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 enhances the quickstart documentation for Windows users by providing crucial guidance for executing a specific installation command. It addresses a potential issue where the command might fail if not run in PowerShell, ensuring a smoother setup experience. Additionally, it refines the language around installation prompts to be more accurate, preventing user confusion by removing the mention of non-existent interactive prompts.

Highlights

• Documentation Clarity for Windows: Added a specific instruction for Windows users to run a particular installation command in PowerShell, as the command with semicolons may fail in the standard command-line interface.
• Installation Prompt Correction: Updated the quickstart guide to accurately reflect the installation process by changing 'Follow the interactive prompts' to 'Follow the instructions', clarifying that there are no interactive prompts during this step.

🧠 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 correctly addresses an issue for Windows users in the quickstart guide. By adding the 'Run in PowerShell' instruction, it clarifies how to execute the chained commands. The update from 'interactive prompts' to 'instructions' is also accurate for the Windows installation process. I have one minor suggestion to improve the consistency of the documentation.

[JanPokorny]

see comment