Skip to content

Latest commit

 

History

History
34 lines (18 loc) · 1.79 KB

CONTRIBUTING.md

File metadata and controls

34 lines (18 loc) · 1.79 KB
Raw

How to contribute to SQribe

Did you find a bug?

  • 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. We fix what we can't see.

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.

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 SQribe will generally not be accepted. Instead, let us know about the cosmetic changes you'd like to make and we will handle the rest. This excludes code documentation, which can be a pull request.

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

  • Suggest your change in the issues area.
  • Once we've collected enough positive feedback about the change we will evaluate the viability of the request.

Do you have questions about the source code?

Do you want to contribute to the SQribe documentation?

SQribe is a volunteer effort. We encourage you to pitch in and join! Reach out to tyhe Fynydd team at the SQribe website to offer your services.

Thanks! ❤️

SQribe Team