docs: use mise activate for PowerShell in getting-started

[rileychh]

Summary

• Replace the outdated shims-to-PATH snippet in the getting-started page's Windows/PowerShell section with mise activate pwsh, matching the pattern used for all other shells
• Keep the profile creation helper and non-PowerShell fallback note

Ref: #8090

[gemini-code-assist]

Summary of Changes

Hello @rileychh, 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 refines the getting-started documentation by modernizing the recommended method for activating mise within PowerShell environments. The change ensures a more consistent and streamlined setup experience for Windows users, bringing the PowerShell instructions in line with those provided for other shell types.

Highlights

• Documentation Update: Replaced the outdated manual shims-to-PATH snippet for Windows PowerShell in the getting-started guide.
• Consistent Activation: Updated the PowerShell activation method to use mise activate pwsh, aligning it with the pattern used for other shells.
• Retained Information: Maintained the instructions for PowerShell profile creation and the fallback note for non-PowerShell users.

Changelog

• docs/getting-started.md
  • Replaced the manual PATH modification instructions for PowerShell with a call to (&mise activate pwsh) | Out-String | Invoke-Expression.
  • Updated the text to consistently use 'PowerShell' with correct capitalization.

Activity

• No human activity has been recorded on 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the getting-started documentation for PowerShell users by replacing the outdated manual PATH modification with the recommended mise activate pwsh command. This aligns the PowerShell instructions with other shells. The changes also include correcting the capitalization of 'PowerShell' for consistency. I've suggested a minor clarification for non-PowerShell users on Windows to make the instructions more explicit.

[gemini-code-assist]

For better clarity, it would be helpful to specify the environment variable for the home directory, as <homedir> can be ambiguous. For Command Prompt (cmd.exe), this would be %USERPROFILE%. The suggestion below clarifies this for the user.

Suggested change

	- If not using PowerShell, add `<homedir>\AppData\Local\mise\shims` to `PATH`.
	- If not using PowerShell (e.g., in Command Prompt), add `%USERPROFILE%\AppData\Local\mise\shims` to `PATH`.

[Copilot]

Pull request overview

Updates the Windows/PowerShell portion of the getting-started guide to use mise activate (consistent with other shells) instead of the older “add shims to PATH” snippet, aligning the docs with current recommended usage.

Changes:

• Replaced the PowerShell “shims-to-PATH” example with (&mise activate pwsh) | Out-String | Invoke-Expression.
• Kept the helper snippet for creating/opening the PowerShell profile.
• Standardized “PowerShell” capitalization in the surrounding text and fallback note.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.