Closed llaville closed 11 months ago
Here is a preview of the new Composer script in action
The results are obtained before to tagging the code with git tag -a 9.1.0
command (i.e)
No problem
Laurent Laville @.***>于2023年12月16日 周六22:54写道:
Here is a preview of the new Composer script in action
composer_qa_check.png (view on web) https://github.com/overtrue/phplint/assets/364342/6c0390cf-83cf-477f-973d-16abf48cd22f
The results are obtained before to tagging the code with git tag -a 9.1.0 command (i.e)
— Reply to this email directly, view it on GitHub https://github.com/overtrue/phplint/issues/199#issuecomment-1858836787, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALHOYFMCRTAGDVIV253A3TYJWYY7AVCNFSM6AAAAABAXUNCLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHAZTMNZYG4 . You are receiving this because you were mentioned.Message ID: @.***>
As lot of others application that provide a Symfony Console Application, PHPLint suffer to a hard-coded concept about Application versionning.
Look at https://github.com/overtrue/phplint/blob/9.1/src/Console/Application.php#L39
As maintainer of application, if we forgot to change VERSION value before publish a new version, we will keep an outdated version number on all official versions : including PHAR and Docker distributions.
To avoid such issue, here is my proposal :
Add a new PHP CS Fixer to check and fix
Application::VERSION
on a git push hook via Composer.composer.json
patchWith new PHP CS Fixer config file
.php-cs-fixer.release.php
And new Fixer
TIP When we still want to push additional code to repository before the final release, we can by pass the
qa:check
failures if any, with the--no-verify
option ofgit push
command.This is the same solution, if we want to by pass
style:fix
on pre-commit git hook :git commit --no-verify
@overtrue Tell me if you're agree to add a such solution !