PowerShell / PowerShell/PSResourceGet
Either finish this Version or Update PowerShellGetv2 with my Bugfix already
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Hi, please either finish development of this version of PowerShellGet already or accept my Bugfix for PowerShellGetv2:
https://github.com/PowerShell/PowerShellGetv2/pull/592
The fix is literally just one line. You delete one line in an if statement and it is fixed.
You still send out PowerShell Core 7 with the same f-ing Bug in PowerShellGet which will reinstall all Scripts to the User-Scope instead of the scope they were installed in when you update them via Update-Script. I sent you a fix, you said you will instead develop this version of PowerShellGet. But not only is this taking forever, you even shipped out a new Version 2.2.5 of PowerShellGetv2 WITHOUT my bugfix (I've fixed it in 2.2.3 already). I don't believe this >:[
Please, fix this Bug NOW for PowerShell Core 7, I can't use your newest product on our servers because you're not fixing this!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Update-Script behavior in the current repository and compare it with the one-line fix described in PowerShellGetv2 PR #592. Reproduce the reported scope change during an update, then confirm that scripts remain in their original installation scope without regressing the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100