Skip to content

Latest commit

 

History

History
29 lines (15 loc) · 1.44 KB

CONTRIBUTING.md

File metadata and controls

29 lines (15 loc) · 1.44 KB

How to contribute to Gazer

Did you read the code of conduct?

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.

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.

  • Depending on the content of the patch, we may need to work out a legal agreement to clarify everyone's rights before the patch is accepted.

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

  • Again please open an issue in GitHub. Larger projects often segregate bugs from new features and enhancements, but we are still small enough that it is not an issue.

Do you have questions about the source code?

Thanks! ❤️ ❤️ ❤️

Gazer Team