CONTRIBUTING.md

How to contribute to Slabbo

Did you find a bug?

• Do not open up a GitHub issue if the bug is a security vulnerability in Slabbo, and instead to 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 a executable test case demonstrating the expected behavior that is not occurring.

• If possible, use the relevant bug report templates to create the issue.

Did you write a patch that fixes a bug?

• 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 ensure you're following the existing code style, and that you've tested the patch appropriately.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of Slabbo will generally not be accepted, but you are free to submit them regardless.

Do you intend to add a new feature or change an existing one?

• Open a new GitHub pull request with the patch.

• Ensure the PR description clearly describes the feature or change. Include the relevant issue number if applicable.

• Before submitting, please ensure you're following the existing code style, and that you've tested the patch appropriately.

Do you have questions about the source code?

• Ask any question about how to use Slabbo in the Slabbo Discord.

Thanks! ❤️ ❤️ ❤️

Mackan