test for pr checks by t-lipingma · Pull Request #1696 · PowerShell/PSScriptAnalyzer

PR Summary

As you can see,
most of PR failed in some necessary checks and it may lie in the two tests of UseCompatibleTypes.Tests.ps1& UseCompatibleCommands.Tests.ps1.

Now I just revised the comment and created a pr to test it.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

This is a worrying error. Annoyingly I can't reproduce it locally, but will see if I can use the CI scripts to do so

/azp run

Closing now that #1697 is merged