Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to PHPCSStandards/PHP_CodeSniffer #33

Closed
slaFFik opened this issue Dec 1, 2023 · 2 comments
Closed

Switch to PHPCSStandards/PHP_CodeSniffer #33

slaFFik opened this issue Dec 1, 2023 · 2 comments

Comments

@slaFFik
Copy link
Member

slaFFik commented Dec 1, 2023

First, read this issue: squizlabs/PHP_CodeSniffer#3932

Then, modify our composer.json to use https://github.com/PHPCSStandards/PHP_CodeSniffer instead of the abandoned https://github.com/squizlabs/PHP_CodeSniffer

@jrfnl
Copy link

jrfnl commented Dec 7, 2023

Thank you for your support and your enthousiasm embracing the take-over of the PHP_CodeSniffer package.

In contrast to earlier information, arrangements are now being made to allow the package to continue under its original name on Packagist. The commit (in the new repo) to rename the package has been reverted.

Sorry for the confusion and thank you for understanding. I hope you'll enjoy the 3.8.0 release, which I expect to release this Friday.

@slaFFik
Copy link
Member Author

slaFFik commented Dec 7, 2023

@jrfnl Thank you again so much for the work you do. And even this gesture of yours to contact all the repos who made (or planning to make) the switch to a new repo PHPCSStandards/PHP_CodeSniffer says and means a lot.

As the situation is resolved, we can continue using the same package.

@slaFFik slaFFik closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants