The following is a set of guidelines for contributing to jest-canvas-mock. These are mostly guidelines, not rules. Use your best judgement, and feel free to proposse changes to this document in a pull request.
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code.
Bugs and enhancement suggestions are tracked as GitHub issues.
After you've determined which repository your bug is related to and that the issue is still present in the latest version of the master branch, create an issue on that repository and provide the following information:
- Use a clear and descriptive title for the issue to identify the problem.
- Explain which behavior you expected to see instead and why.
- Describe the exact steps to reproduce the problem in as many details as necessary.
- When providing code samples, please use code blocks.
Instructions are similar to those for bug reports. Please provide the following information:
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a description of the suggested enhancement in as many details as necessary.
- When providing code samples, please use code blocks.
Instructions are similar to those for bug reports. Please provide the following information:
- Use a clear and descriptive title for the pull request.
- Provide a description of the suggested changes in as many details as necessary.
- Document your new code where necessary.
- Please refrain from refactoring (unrelated code) as it makes your pull request easier to review.
- Create tests for your new code where necessary. For creating or updating tests, please see the Test Instructions.
Before submitting your pull request, please make sure that the following conditions are met:
- Your new code adheres to the code style through running
npm run prettier. - Your new code passes all existing and new tests through running
npm test. - You appended yourself to the list of contributors in the README file.