github.
Use the github issue tracker to signal an issue.
This project is open source, and as such, the maintainers give their free time to build and maintain the source codeheld within. They make the code freely available in the hope that it will be of use to other developers. It would beextremely unfair for them to suffer abuse or anger for their hard work.
Contributions are welcome.
Please, send your contribution via a github pull request on Puswhord/Puswhord.
The code is mainly organised in a mono-repo, learn more about the code architecture
See Code Architecture ➜ Development environement
The docs is inside the main repo, you will find write in markdown in packages/docs/content.
On each PR, the docs is compiled for the current release and published pushword.piedweb.com by a github action.
When requesting or submitting new features, first consider to create a dedicated extension.
If your extension reply to an important community need, you can create a pull request to merge it in this Mono Repo. It will permit to maintain easily it compatibility in next Puswhord update. Moreover, extension will be tested at each commit on one of Pushword's package.
Else, consider create it own git repo and create a Pull Request on the doc to add a link to this fresh extension. The link will be accepted if your extension is well tested and fully functionnal.
This project respect PSR-12 Coding standard. Before your pull-request, run php-cs-fixer
.
composer format
composer test
# and to test with --prefer-lowest
composer test full
This attention would be nice :
Add tests
Document any change in behaviour - Make sure the 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.
One pull request per feature - If you want to do more than one thing, send multiple pull requests.
Happy coding!