PowerShell / PowerShell/PSScriptAnalyzer
How do you incorporate PSScriptAnalyzer as part of your dev process?
未關閉
還沒有人認領這個 Issue。
Issue - Discussion
Issue - Question
- 主要語言
- C#
- 星號
- 2.2k
- 分支
- 415
- 平均合併
- 13 小時 1 分鐘
- 30 天內合併 PR
- 2
描述
My team wants to leverage this utility to ensure consistent coding practices for all of our custom commandlets. I was hoping to have a discussion and get some insight into how other teams and developers use PSScriptAnalyzer as part of their dev process.
Some questions to get this going:
- What triggers your analysis? Is it manually run by developers as needed? Does it run as part of your postbuild process? Only in certain build configurations? If it does run with each build, does the build fail if Warnings or Errors are generated?
- Are the results only for the developer running the analysis to review in their console, or do you take the results and do something with them?
- How have you addressed performance issues / slowdowns caused by analysis of many Powershell scripts at once?
I realize all teams and organizations are different, and one team's process isn't necessarily going to work for everyone, but I am interested in recommendations for what processes you find work well for yourself and your team.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
此 issue 未指明任何檔案、測試或進入點。它要求針對 PSScriptAnalyzer 提供流程建議,包括觸發條件、建置行為、結果處理和效能。沒有為首次貢獻者定義具體的完成標準。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- powershell
- 領域
- tooling
- Issue 類型
- 文件
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 15/100