When PRs #38528 and #38527 are merged, the hard errors would be solved in our codebase. The issues left would be several warnings and 3 errors regarding soft reserved keywords which we are using. Those issues couldn't be solved and should be part of the exclusion list.
Either this needs to be split into chunks with propper teating instructions or rebased to 5.0 and merged there early. But I wouldn't merge this in a minor only by code review.
I've split this PR up into 5 PRs, see above. When those are merged and they are upmerged into this branch, that should leave only the code to introduce the version check in phpcs. I don't think it is usefull to solve the conflicts before those are merged, since each will introduce new conflicts...
Is anything happening with this? It has not been touched for over a year and it is unclear if anything will ever happen. It refers to it being partialy split into 5 pr but some of those have been closed as abandoned.
When PRs #38528 and #38527 are merged, the hard errors would be solved in our codebase. The issues left would be several warnings and 3 errors regarding soft reserved keywords which we are using. Those issues couldn't be solved and should be part of the exclusion list.