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.
If possible, use the relevant bug report templates to create 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.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of FunKey-OS will generally not be accepted. I know this might be thinking, «sure, it might not be adding much value, but I already wrote the code, so the cost is already paid – by me – so why not just merge it»? The reason is that there are a lot of hidden cost in addition to writing the code itself.
It’s awesome that you want to contribute to FunKey-OS, please keep the PRs coming! All we ask is that you refrain from sending these types of changes in the future (and read the contribution guide :). I hope you’ll understand!
Suggest your change in the FunKey-OS Discord development channel and start writing code.
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.
Thanks! :heart: :heart: :heart:
The FunKey-OS Team