👷 Add GitHub workflow for linting and code validation - #5
Conversation
Sorry, something went wrong.
This comment was marked as resolved.
|
Warning Rate limit exceeded@rickyheijnen has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 30 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📥 CommitsReviewing files that changed from the base of the PR and between efc3e23 and cd5587d. 📒 Files selected for processing (2)
\n\n## Walkthrough\nAdds two GitHub Actions workflows under .github/workflows: one to run PHP CS Fixer in dry-run mode on push with caching and failure artifacts, and another to run PHPStan static analysis across PHP 7.4–8.3 with caching, conditional config selection, and artifact upload on failure.\n\n## Changes\n| Cohort / File(s) | Summary of changes |\n| --- | --- |\n| CI workflows Comment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
🔍 Summary
This PR adds comprehensive GitHub Actions workflows for automated code quality checks including linting, static analysis, and validation across multiple file types and PHP versions.
📝 Description
💬 Additional information
The workflows are designed to run on every push and provide comprehensive code quality checks. The static analysis runs across multiple PHP versions to ensure compatibility, while the linting workflows validate various file formats commonly used in PHP projects.