Skip to content

Improve Composer-based developer workflow and fix PHPCS/PHPStan issues - #1296

Closed
Marcus-Nightingale wants to merge 10 commits into
vrana:masterfrom
Marcus-Nightingale:ci-cleanup
Closed

Improve Composer-based developer workflow and fix PHPCS/PHPStan issues#1296
Marcus-Nightingale wants to merge 10 commits into
vrana:masterfrom
Marcus-Nightingale:ci-cleanup

Conversation

@Marcus-Nightingale

Copy link
Copy Markdown
Contributor

This change updates the project’s Composer workflow so developers can run checks more easily and CI uses the same entry points.

Main changes:
• Added Composer scripts for phpcs, phpcbf, and phpstan
• Added fallback behavior so the coding tools can run from vendor/bin, a global Composer install, or PATH
• Updated CI to run composer phpcs and composer phpstan directly
• Fixed the PHPStan config and resolved the PHPStan issues reported on this branch
• Fixed the PHPCS issues reported on this branch
• Updated the README with the Composer-based coding standard commands
• Confirmed composer compile still works

Validation:
• composer phpcs
• composer phpstan
• composer compile

@vrana

vrana commented Jul 7, 2026

Copy link
Copy Markdown
Owner

I'm not interested in adding the empty lines everywhere.

@vrana vrana closed this Jul 7, 2026
@Marcus-Nightingale

Copy link
Copy Markdown
Contributor Author

No worries i will take this out and add in the rule to exclude the warning 👍🏻 is there anything else in terms of the code styling you don't like etc?

@vrana

vrana commented Jul 7, 2026

Copy link
Copy Markdown
Owner

I want to keep everything as is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants