You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be quite useful if I could use thehttps://pre-commit.com/tool to run PSScriptAnalyzer on my powershell scripts during the git commit stage. then I could find problems in my powershell code before they land into git repositories.
information how about to write a pre-commit hook can be found at https://pre-commit.com/#new-hooks
Proposed technical implementation details (optional)
for example, a pre-commit hook for pylint (the python linter) is at https://github.com/pylint-dev/pylint
The text was updated successfully, but these errors were encountered:
@winterz What do you expect PSScriptAnalyzer to do to enable that? Because it is a PowerShell based tool and therefore not in the list of supported languages here: https://pre-commit.com/#supported-languages
But it has script support so I assume that goes to bash or cmd depending on OS and you could write a small script that calls PowerShell to then call PSScriptAnalyzer and use the -EnableExitCode switch to signal success/failure
it would be quite useful if I could use the
https://pre-commit.com/
tool to run PSScriptAnalyzer on my powershell scripts during the git commit stage. then I could find problems in my powershell code before they land into git repositories.information how about to write a pre-commit hook can be found at
https://pre-commit.com/#new-hooks
Proposed technical implementation details (optional)
for example, a pre-commit hook for pylint (the python linter) is at
https://github.com/pylint-dev/pylint
The text was updated successfully, but these errors were encountered: