Contributing

Contributions are welcome and will be fully credited.

We accept contributions via Pull Requests on Github.

Pull Requests

PSR-12 Coding Standard - Check the code style with $ composer check-style and fix it with $ composer fix-style.
Add tests! - Your patch won't be accepted if it doesn't have tests.
Fix any issues Psalm raises - It's not necessarily a deal breaker if Psalm throws an error on your pull request that simply can't be resolved, but please run it with $ composer psalm, and do your best to fix any issues it raises before submitting your pull request. We try to keep the code base as type-safe as possible, and Psalm is a big part of that.
Document any change in behaviour - Make sure the README.md and any other relevant documentation are kept up-to-date.
Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.
Create feature branches - Don't ask us to pull from your master branch.
One pull request per feature - If you want to do more than one thing, send multiple pull requests.
Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

$ composer test

Happy coding!