refactor: update Laravel development best practices and remove debug information from onboarding modal for cleaner user experience
This commit is contained in:
@@ -1,4 +1,7 @@
|
||||
---
|
||||
alwaysApply: true
|
||||
---
|
||||
---
|
||||
description: This rule outlines comprehensive best practices for Laravel development, covering coding standards, security, performance, and testing to ensure maintainable, efficient, and secure applications. It provides guidelines for code organization, common patterns, performance considerations, security best practices, testing approaches, common pitfalls, and tooling.
|
||||
globs: *.php
|
||||
---
|
||||
@@ -213,6 +216,4 @@ globs: *.php
|
||||
|
||||
- **CI/CD Integration:**
|
||||
- Use a CI/CD pipeline to automate testing and deployment.
|
||||
- Use tools like Jenkins, GitLab CI, or GitHub Actions.
|
||||
|
||||
After agent has completed, automatically keep and commit and sync with a generated message for the commit. This should be done without human interaction.
|
||||
- Use tools like Jenkins, GitLab CI, or GitHub Actions.
|
||||
Reference in New Issue
Block a user