Contribution Guide

• Bug Reports
• Support Questions
• Security Vulnerabilities

Bug Reports

To encourage active collaboration, Laravel Hyperf strongly encourages pull requests, not just bug reports. Pull requests will only be reviewed when marked as "ready for review" (not in the "draft" state) and all tests for new features are passing. Lingering, non-active pull requests left in the "draft" state will be closed after a few days.

However, if you file a bug report, your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.

Remember, bug reports are created in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the bug report will automatically see any activity or that others will jump to fix it. Creating a bug report serves to help yourself and others start on the path of fixing the problem. If you want to chip in, you can help out by fixing any bugs listed in our issue trackers. You must be authenticated with GitHub to view all of Laravel Hyperf's issues.

If you notice improper DocBlock, PHPStan, or IDE warnings while using Laravel Hyperf, do not create a GitHub issue. Instead, please submit a pull request to fix the problem.

Support Questions

Laravel Hyperf's GitHub issue trackers are not intended to provide Laravel Hyperf help or support. Instead, use GitHub Discussions

Security Vulnerabilities

If you discover a security vulnerability within Laravel Hyperf, please send an email to Albert Chen at albert@laravel-hyperf.com. All security vulnerabilities will be promptly addressed.