25 lines
770 B
Markdown
25 lines
770 B
Markdown
|
# Contributing to Phred
|
||
|
|
|
||
|
|
Thank you for your interest in Phred! We welcome contributions of all kinds.
|
||
|
|
|
||
|
|
## RFC Process
|
||
|
|
|
||
|
|
For major changes, please open an issue first to discuss what you would like to change.
|
||
|
|
|
||
|
|
1. Create a "Request for Comments" (RFC) issue.
|
||
|
|
2. Wait for feedback from the core maintainers.
|
||
|
|
3. Once approved, submit a Pull Request.
|
||
|
|
|
||
|
|
## Pull Request Process
|
||
|
|
|
||
|
|
1. Fork the repository and create your branch from `main`.
|
||
|
|
2. If you've added code that should be tested, add tests.
|
||
|
|
3. Ensure the test suite passes (`composer test`).
|
||
|
|
4. Ensure static analysis passes (`composer analyze`).
|
||
|
|
5. Ensure code style matches PSR-12 (`composer fix`).
|
||
|
|
6. Update the documentation if necessary.
|
||
|
|
|
||
|
|
## Code of Conduct
|
||
|
|
|
||
|
|
Please be respectful and professional in all interactions.
|