34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Contributing to Flux CMS
|
|
|
|
We welcome contributions from the community! Thank you for your interest in making Flux CMS better.
|
|
|
|
## How to Contribute
|
|
|
|
### Reporting Bugs
|
|
|
|
- Use the GitHub issue tracker to report bugs.
|
|
- Please include a clear title and description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
|
|
|
|
### Suggesting Enhancements
|
|
|
|
- Use the GitHub issue tracker to suggest new features or enhancements.
|
|
- Clearly describe the proposed enhancement and the motivation for it.
|
|
|
|
### Pull Requests
|
|
|
|
1. **Fork the repo** and create your branch from `main`.
|
|
2. **Add tests!** Your patch won't be accepted if it doesn't have tests.
|
|
3. **Ensure the test suite passes.**
|
|
4. **Follow the coding style.** Please follow the PSR-12 coding standard.
|
|
5. **Write a clear commit message.**
|
|
6. **Issue that pull request!**
|
|
|
|
## Coding Style
|
|
|
|
Flux CMS follows the [PSR-12](https://www.php-fig.org/psr/psr-12/) coding standard. You can use tools like PHP-CS-Fixer to automatically format your code.
|
|
|
|
## Code of Conduct
|
|
|
|
We expect all contributors to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). Please be respectful and considerate of others.
|
|
|
|
Thank you for your contribution!
|