Doc: Added powershell installation link to the guide

[Lymah123]

Summary

Fixed Windows PowerShell installation link not included in the installation guide.

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other (specify below)

Testing

Related Issues

Relates to #4469
Discussion: LINK (if any)

Screenshots/Demos (for UX changes)

Before:

After:

Email:

[Lymah123]

Hi @blackgirlbytes, I will be waiting for feedback on this PR.

[cbruyndoncx]

@angiejones TEST PASSED:

1. Started regular "Windows Powershell" in Windows Terminal
2. ran Invoke-webrequest per documentation line to download the script
3. ran script - here is the output, it starts the configuration automatically, it is shared with the gui, same location, so i cancelled out.

PS C:\Users\bruyn> .\download_cli.ps1
Downloading stable release: goose-x86_64-pc-windows-gnu.zip...
Download completed successfully.
Created temporary directory: C:\Users\bruyn\AppData\Local\Temp\goose_install_329962586
Extracting goose-x86_64-pc-windows-gnu.zip to temporary directory...
Extraction completed successfully.
Found goose-package subdirectory, using that as extraction directory
Moving goose to C:\Users\bruyn.local\bin\goose.exe
Moving temporal-service to C:\Users\bruyn.local\bin\temporal-service.exe
Moving temporal CLI to C:\Users\bruyn.local\bin\temporal.exe
Moving Windows runtime DLL: libgcc_s_seh-1.dll
Moving Windows runtime DLL: libstdc++-6.dll
Moving Windows runtime DLL: libwinpthread-1.dll
Cleaned up temporary directory.

Configuring goose

This will update your existing config file
if you prefer, you can edit it directly at C:\Users\bruyn\AppData\Roaming\Block\goose\config\config.yaml

┌ goose-configure
│
◇ What would you like to configure?
│ Toggle Extensions
│
■ enable extensions: (use "space" to toggle and "enter" to submit)
│ developer
└ Operation cancelled.

Warning: goose installed, but C:\Users\bruyn.local\bin is not in your PATH.
To add it to your PATH permanently, run the following command as Administrator:
[Environment]::SetEnvironmentVariable('PATH', $env:PATH + ';C:\Users\bruyn.local\bin', 'Machine')

Or add it to your user PATH (no admin required):
[Environment]::SetEnvironmentVariable('PATH', $env:PATH + ';C:\Users\bruyn.local\bin', 'User')

For this session only, you can run:
$env:PATH += ';C:\Users\bruyn.local\bin'

goose CLI installation completed successfully!
goose is installed at: C:\Users\bruyn.local\bin\goose.exe
PS C:\Users\bruyn>

[taniandjerry]

Still waiting on one test, any reason why?

[iandouglas]

@DOsinga any idea what this is stuck on?

[EbonyLouis]

@Lymah123 Hey, thank you for contributing, we have one test left to run, can you fetch and merge main into your PR please

After that, we should be all set to merge 🥳

[Lymah123]

@Lymah123 Hey, thank you for contributing, we have one test left to run, can you fetch and merge main into your PR please

After that, we should be all set to merge 🥳

Done @EbonyLouis !

[EbonyLouis]

@Lymah123 thanks, that ddin't seem to do the trick can you try these steps in your terminal please?:

1. make sure you're on your branch:

git checkout powershell

2. do this step if you haven't already:

git remote add upstream https://github.com/block/goose.git

3. Fetch latest from both remotes:

git fetch upstream
git fetch origin

4. Merge our main into your branch and push:

git merge upstream/main 
git push                  

If you need any help, lmk 💖

[blackgirlbytes]

Merging! Thanks for your contribution!