Skip to content

fixed issue "Remove-FinOpsHub fails when there's only one resource" #435

fixed issue "Remove-FinOpsHub fails when there's only one resource"

fixed issue "Remove-FinOpsHub fails when there's only one resource" #435

Triggered via pull request September 14, 2024 19:20
Status Success
Total duration 1m 22s
Artifacts

dev.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
Pester
[-] Should pass rule [PSAvoidTrailingWhitespace] 113ms (111ms|2ms)
Pester
[-] Should pass rule [PSAvoidUsingEmptyCatchBlock] 8ms (8ms|0ms)
Pester
[-] Should pass rule [PSAvoidTrailingWhitespace] 5ms (5ms|0ms)
Pester
[-] Should pass rule [PSUseOutputTypeCorrectly] 7ms (7ms|0ms)
Pester
[-] Should pass rule [PSAvoidTrailingWhitespace] 5ms (4ms|0ms)
Pester
[-] Should pass rule [PSUseOutputTypeCorrectly] 7ms (6ms|1ms)
Pester
[-] Should pass rule [PSAvoidTrailingWhitespace] 5ms (5ms|0ms)
Pester
[-] Should pass rule [PSUseBOMForUnicodeEncodedFile] 8ms (8ms|0ms)
Pester
[-] Should pass rule [PSUseProcessBlockForPipelineCommand] 4ms (4ms|0ms)
Pester
[-] Should pass rule [PSUseProcessBlockForPipelineCommand] 4ms (4ms|0ms)
Pester
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/