Juliette

Also mentioned/discussed in #66 Info on the change for the handbook update workflow can be found here: https://github.com/WordPress/wpcs-docs/pull/66#issuecomment-1114686803

> Out of curiosity, what do you think about automating the generation and update of `changelog.md` as a pre-commit hook? > > ```shell > LATEST=$(git log -n 20 --pretty="- %cd...

> Adding a descriptive commit subject line when committing directly to the main branch or when merging a PR would make the history more descriptive and remove the need for...

> The GPLv2 states: > > > You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. >...

Not sure if it needs a separate section, but improving the text of this section seems valid.

> If we add readonly and we split this to properties and methods, should we have a paragraph for `readonly` classes as well? We just discussed this and I agree,...

@hellofromtonya Correct, but it was only included as too many people don't know how to run `php -l` :cry: Also: "all" PHPCS/WPCS/PHPCompatibility sniffs should give the same results independently of...

I can highly recommend using the [`Parallel-Lint`](https://github.com/JakubOnderka/PHP-Parallel-Lint) package for speedy linting, works on PHP 5.4 and higher, so this might be a good option for when this issue gets addressed.

@jeffpaul Short summary of what was decided regarding this during the meeting at WCEU: * The TRT repo will be renamed to a more generic name and moved to the...

As a sister-issue, I believe it would be good to scan for parse errors too in all PHP versions supported by the plugin/theme. Just running `php -l` over all files...