Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several new configuration and documentation files aimed at standardizing development workflows, enforcing code quality, and establishing project-specific conventions. The main themes are the introduction of automated quality checks, documentation of project rules, and configuration for project-specific tooling.
Automated Quality Checks and Tooling:
.cursor/hooks.jsonfile to run a custom hook that executes a PHPStan analysis (run-phpstan-on-stop.ts) automatically when a stop event occurs, ensuring static analysis is performed on staged changes..cursor/hooks/run-phpstan-on-stop.ts, a Node.js script that checks for Git changes and runs PHPStan with a memory limit, reporting errors in a standardized format..cursor/mcp.jsonto configure the "laravel-boost" MCP server, specifying the command to run Laravel Boost via Artisan.Project and Code Quality Guidelines:
.cursor/rules/laravel-boost.mdc, a comprehensive markdown document detailing Laravel Boost-specific guidelines, PHP and Laravel conventions, testing requirements, and best practices for working with the project's stack and tools..cursor/rules/conventional-commits.mdcto enforce the use of Conventional Commits for all commit messages, including format, types, examples, and rules..cursor/rules/code-formatters.mdcto document the required usage of code formatters and refactoring tools like Rector, ensuring code consistency.These changes collectively enforce higher code quality, clearer documentation, and consistent development practices across the project.