Contributing
Thank you for considering contributing to the Symfony Multi-Tenancy Bundle! π We welcome all suggestions, bug reports, and pull requests. Below are some friendly guidelines to help you get started.
π‘ 1. Suggesting New Featuresβ
We love new ideas! If you have an idea for a feature or improvement:
-
Check the issue tracker to see if itβs already discussed. π
-
Open a new issue with a clear title and detailed description of your proposal:
- What problem does it solve?
- How would it work in practice?
- Any example code or usage patterns.
-
Engage in the discussion: feedback is iterative. π
Alternatively, share your ideas and feedback in our GitHub Discussions forum. π¬
π 2. Contributing Code (Features, Improvements & Fixes)β
Ready to contribute code whether adding new features, fixing bugs, or improving existing functionality? Follow these steps:
-
Fork the repository to your own GitHub account. π΄
-
Create a feature branch named descriptively, e.g.,
feature/performance-optimizations
orbugfix/fix-connection-error
. πΏ -
Implement your changes, adhering to the projectβs coding standards and adding tests for any new or modified behavior. π
-
Update documentation (in
docs/
) to cover your changes. π -
Submit a Pull Request against the
main
branch, referencing the related issue(s). Include:- A summary of your changes. ποΈ
- Usage examples or migration steps if applicable. π
- Any breaking changes or compatibility notes. β οΈ
π¨ 3. Code Styleβ
Please follow these conventions:
-
PSR-12 coding standard. π―
-
Declare strict types in PHP files:
declare(strict_types=1);
-
Add docblocks for all public methods and complex logic. π
-
Run and fix issues with:
composer fix
β 4. Running Testsβ
We use PHPUnit to ensure quality. To run the full test suite:
composer install
vendor/bin/phpunit --testsuite=unit
vendor/bin/phpunit --testsuite=integration
- Ensure both main and tenant logic are covered by tests. π‘οΈ
- Add new tests for any bug fixes or features. π§ͺ
- CI will run tests automatically on PRs. βοΈ
We appreciate every contributionβbig or small. By following these guidelines, you help keep the project maintainable and high-quality. Happy coding! π