-
-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add code of conduct, update changelog
- Loading branch information
Showing
3 changed files
with
94 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment include: | ||
|
||
- Using welcoming and inclusive language | ||
- Being respectful of differing viewpoints and experiences | ||
- Gracefully accepting constructive criticism | ||
- Focusing on what is best for the community | ||
- Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
- The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
- Trolling, insulting/derogatory comments, and personal or political attacks | ||
- Public or private harassment | ||
- Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
- Other conduct which could reasonably be considered inappropriate in a professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version] | ||
|
||
[homepage]: https://contributor-covenant.org | ||
[version]: https://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# Contributing | ||
|
||
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. | ||
|
||
## Code of Conduct | ||
|
||
This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. | ||
|
||
## Filing Issues | ||
|
||
Bugs and enhancement suggestions are tracked as GitHub issues. | ||
|
||
#### How Do I Submit A (Good) Bug Report? | ||
|
||
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](https://help.github.com/articles/creating-and-highlighting-code-blocks/). | ||
|
||
#### How Do I Submit A (Good) Enhancement Suggestion? | ||
|
||
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](https://help.github.com/articles/creating-and-highlighting-code-blocks/). | ||
|
||
## Submitting Pull Requests | ||
|
||
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](./__tests__). | ||
|
||
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](./README.md) file. |