Thank you for considering contributing to Project Template! Please take a moment to review this guide to ensure your contributions align with the project's standards and goals.
To encourage active collaboration, we strongly encourage bug reports to follow these guidelines:
- Search existing issues before submitting a new one.
- If the issue does not already exist, create a new issue.
- Include the following details:
- A descriptive title.
- Steps to reproduce the issue.
- Expected behaviour.
- Actual behaviour.
- Environment details (Laravel version, PHP version, etc.).
- Provide as much context as possible to help maintainers understand the issue.
Issues that do not meet these requirements may be closed without further explanation.
We do not provide support through the issue tracker. If you have a question, consider asking in:
To propose a significant new feature, start by opening an issue. Please include as much detail as possible, including potential use cases and examples. This ensures maintainers can discuss the feature before significant development is undertaken.
We accept contributions in the form of pull requests. To submit a pull request:
- Fork the repository.
- Create a branch for your changes:
git checkout -b feature/your-feature-name
- Make your changes in this branch.
- Ensure your code adheres to the style guide and passes all tests.
- Submit a pull request to the
main
branch.
Project Template adheres to PSR-12 coding standards and uses Laravel’s conventions. To ensure consistency, run the following commands before committing your changes:
- PHP Formatting:
composer format
- JavaScript/TypeScript Formatting:
npm run lint
Before submitting your changes, ensure all tests pass:
- Run the test suite:
php artisan test
- Add new tests for any new features or bug fixes.
If you discover a security vulnerability in this project, please report it privately by emailing [email protected]. Security vulnerabilities will be promptly addressed.
Thank you for your contributions!