-
Do not open up a GitHub issue if the bug is a security vulnerability in Pawpaw, and instead to refer to the security policy.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Open a new GitHub pull request with your patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
If you have a suggestion that would make this better, please fork the repo and create a pull request.
-
You can also simply open an issue with the tag "enhancement".
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Rails will generally not be accepted.
- Ask Robert any question about how to use PawPaw via [email protected].
- I'd love to hear feedback on expanding or improving documents.
Thanks! ❤️ ❤️ ❤️
Robert