Skip to content

Issues: PowerShell/PSScriptAnalyzer

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
15 Open 109 Closed
15 Open 109 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Pester: Install latest version on WMF builds and skip installation if version is new enough for Azure DevOps which now ships with Pester Area - Build
#1629 opened Jan 23, 2021 by bergmeister • Draft
6 tasks done
1
Add version to PSScriptAnalyzer assemblies Area - Build Issue - Enhancement
#1537 opened Jul 1, 2020 by rjmholt
1
Offer test result output for CI Area - Build Issue - Enhancement
#1296 opened Jul 25, 2019 by rjmholt
3
Add a test for copyright headers for CI Area - Build Issue - Enhancement
#1155 opened Feb 28, 2019 by rjmholt
Start using PowerShell Standard 3 Area - Build Consider - 2.0 Issue - Enhancement
#1022 opened Jun 12, 2018 by bergmeister
1
MS Internal - VSTS build scripts will need changing Area - Build not ready
#993 opened May 8, 2018 by JamesWTruher
@JamesWTruher
PSSA should be crossgen'd Area - Build
#991 opened May 8, 2018 by SteveL-MSFT
3
Being able to run tests by setting $PsModulePath instead of XCopy to one of those folders Area - Build
#965 opened Apr 8, 2018 by bergmeister
Investigate/Fix test failure on PowerShell Core Area - Build Area - Rules
#944 opened Mar 23, 2018 by bergmeister
1
Should the 'Microsoft.Windows.PowerShell.ScriptAnalyzer' namespace/assembly names be renamed to 'Microsoft.PowerShell.ScriptAnalyzer' ? Area - Build Consider - 2.0 Issue - Enhancement
#920 opened Mar 3, 2018 by bergmeister
8
Compiler warning in UseCompatibleCmdlets class due unfinished feature with # if DEBUG pragma -> consider removal to allow us to use the /warnaserror compiler option Area - Build Up-for-Grabs
#913 opened Feb 28, 2018 by bergmeister
@bergmeister
WIP: Roadmap for script analyzer Area - Build in progress
#886 opened Feb 12, 2018 by JamesWTruher
1 of 6 tasks
@JamesWTruher
3
Internal: Build/Release inconsistencies compared to PowerShell Core repo Area - Build
#871 opened Feb 5, 2018 by bergmeister
5 of 7 tasks
Consider publishing pre-releases Area - Build Issue - Discussion
#861 opened Jan 31, 2018 by bergmeister
1
Consider appveyor artifact for module Area - Build Issue - Enhancement
#622 opened Sep 26, 2016 by RamblingCookieMonster Backlog
@kapilmb
4
ProTip! What’s not been updated in a month: updated:<2024-12-26.