PowerShell / PowerShell/PSScriptAnalyzer
How do you incorporate PSScriptAnalyzer as part of your dev process?
未关闭
还没有人认领这个 Issue。
Issue - Discussion
Issue - Question
- 主要语言
- C#
- 星标
- 2.2k
- 派生
- 414
- 平均合并
- 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