It wont come as a surprise to anyone who has been watching this project, but I've had very little time to work on PHP_CodeSniffer over the last couple of years, and the last 12 months in particular. The result is that the PR backlog isn't being worked through, releases are infrequent, and the project isn't keeping up with PHP syntax changes.
To help, @jrfnl has been given write access to the repository as of today. Together, we'll work through the backlog of PRs and feature requests, so expect to see commits and merges coming from both of us.
@jrfnl has been the top contributor to PHP_CodeSniffer for several years and worked on most of the new syntax support and testing improvements, as well as working on a number of high-profile packages surrounding PHP_CodeSniffer and the wider PHP community.
Thank you @jrfnl for all your work on PHP_CodeSniffer so far, and I look forward to working with you more closely from now on.
jrfnl
commented
7 months ago
It wont come as a surprise to anyone who has been watching this project, but I've had very little time to work on PHP_CodeSniffer over the last couple of years, and the last 12 months in particular. The result is that the PR backlog isn't being worked through, releases are infrequent, and the project isn't keeping up with PHP syntax changes.
To help, @jrfnl has been given write access to the repository as of today. Together, we'll work through the backlog of PRs and feature requests, so expect to see commits and merges coming from both of us.
@jrfnl has been the top contributor to PHP_CodeSniffer for several years and worked on most of the new syntax support and testing improvements, as well as working on a number of high-profile packages surrounding PHP_CodeSniffer and the wider PHP community.
Thank you @jrfnl for all your work on PHP_CodeSniffer so far, and I look forward to working with you more closely from now on.