-
Notifications
You must be signed in to change notification settings - Fork 13
add some Workflows (Pester, PSScriptAnalyzer) #24
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.
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
base: master
Are you sure you want to change the base?
Conversation
We could put an Something like @{
Run = @{
Path = '.'
}
CodeCoverage = @{
Enabled = $true
}
TestResult = @{
Enabled = $true
}
} Then we could load that file with Let me know if this sounds good so I can create the file and adjust the tests. |
Sounds good to me |
…pped in a getter function as per PSScriptAnalyzer best practices.
I did some restructuring for the script analyzer to be happy, let me know what you think. |
… would be difficult to maintain with all different profile combinations
LGTM |
the Pester worklow gets red if something with Pester fails
and maybe @joakimbergros got a Pester config for us?
e.g. for code scanning:
https://github.com/T0biiias/Modules.QRCodeGenerator/security/code-scanning
after merge:
https://github.com/TobiasPSP/Modules.QRCodeGenerator/security/code-scanning
we can still discuss what should be set here:
https://github.com/TobiasPSP/Modules.QRCodeGenerator/pull/24/files#diff-13c6613fa5775bc9c8a11734f08caf959197561760e0bbd87eafad1adcee3f4dR39