playnite-web-app • Docs
playnite-web-app / CONTRIBUTING
-
Do not open up a GitHub issue if the bug is a security vulnerability, and instead refer to our 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 any relevant screenshots demonstrating the expected behavior that is not occurring. Do not include sensitive information into the issue.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, please read the Playnite Web Conventions guide to know more about coding conventions and general guidelines.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Playnite Web will generally not be accepted.
-
Create an ideas discussion using the pre-defined template.
-
Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
-
Learn more about the RFC feature request process.
- Ask any question about Playnite Web by joining our chat.
Playnite Web is a volunteer effort and we encourage you to pitch in and join!
Thanks! ❤️ ❤️ ❤️