Skip to content

Conversation

@WisdomNwaiwu
Copy link
Contributor

Context

To improve code quality consistency without introducing risky automatic mutations, we are introducing a non-destructive PHP CS Fixer check into the CI pipeline.
Previously, coding-style violations could slip through unnoticed until later stages or manual review.
This change ensures formatting issues are surfaced early while keeping all fixes explicitly developer-controlled.
The goal is visibility and enforcement — not automatic code changes in CI.

Description

A new PHP CS Fixer (check-only) job was added to the CI workflow.
The job runs php-cs-fixer in dry-run mode using the existing .php-cs-fixer.php configuration, failing the workflow if violations are detected while only printing diffs.
No files are modified by CI, and no existing configuration files were changed.
The check runs only when the PR branch is up-to-date with its base branch and blocks further jobs on failure.

Changes in the codebase (optional)

Added a CI job: PHP CS Fixer (Check Only)
Uses existing fixer config (.php-cs-fixer.php)
Executes via Composer script:
"php-cs-fixer fix --dry-run --diff"

No automatic fixes, commits, or repository mutations

Additional information (optional)

CI reports style violations clearly via diff output
Developers must fix issues locally before pushing
This follows the same “check-only” philosophy used for PHPStan and SQL validation
No Discord notification was added for this job to avoid noise; failures are visible directly in CI

Links

  • ClickUp:
  • Additional:

@vidkazan vidkazan removed the 1.11.3 label Dec 23, 2025
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.

3 participants