I think it's more common to use git commit hooks to enforce the sorts of things this PR is trying to catch.

It seems users (IDEs) can silently ignore hooks. So anyway we need scripts to perform approved checks.

An IDE could not ignore a server side hook.

People can all :-)
Even if we add hooks, we still need a script for full code checks, don't we?

With specific regard to hooks, GitHub addins look more attractive. If MSFT can turn such addins for code checks it will be great. Is it possible?

There is code to automatically fix most of the tests you have added here: https://github.com/PowerShell/DscResource.Tests/blob/dev/MetaFixers.psm1

I'd say we separate the hook issue. These tests should be identified in some way that we can create a hook, but we need the tests before we can create a hook.

@TravisEz13 Thanks! We should be careful with MetaFixers.psm1:

• Not all files is UTF8 (I don't risk to fix this) and some files contain special symbols.
• Many test files contain tabs and broken formatting

What is our plan? What should I do next?

This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. Thank you for your contributions.

This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days.
Thank you for your contributions.
Community members are welcome to grab these works.