Skip to content

Commit 9ec508e

Browse files
committed
Adds contributing guidelines, issue template, and code of conduct.
1 parent c5e0c53 commit 9ec508e

File tree

3 files changed

+104
-0
lines changed

3 files changed

+104
-0
lines changed

.github/CONTRIBUTING.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Contributing to this project
2+
3+
[fork]: https://github.com/graphcool/graphql-playground/fork
4+
[pr]: https://github.com/graphcool/graphql-playground/compare
5+
[code-of-conduct]: CODE_OF_CONDUCT.md
6+
7+
Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
8+
9+
Please note that this project is released with a [Contributor Code of Conduct][code-of-conduct]. By participating in this project you agree to abide by its terms.
10+
11+
## Contribution Agreement
12+
13+
As a contributor, you represent that the code you submit is your original work or that of your employer (in which case you represent you have the right to bind your employer). By submitting code, you (and, if applicable, your employer) are licensing the submitted code to the open source community subject to the MIT license.
14+
15+
16+
## Submitting a pull request
17+
18+
0. [Fork][fork] and clone the repository
19+
0. Create a new branch: `git checkout -b feature/my-new-feature-name`
20+
0. Run `npm install` or `yarn install` to make sure you've got the latest dependencies.
21+
0. Make your change
22+
0. Run the unit tests and make sure they pass and have 100% coverage. (`npm test`)
23+
0. Push to your fork and [submit a pull request][pr]
24+
0. Pat your self on the back and wait for your pull request to be reviewed and merged.
25+
26+
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
27+
28+
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
29+
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
30+
- In your pull request description, provide as much detail as possible. This context helps the reviewer to understand the motivation for and impact of the change.
31+
- Make sure that all the unit tests still pass. PRs with failing tests won't be merged.
32+
33+
## Resources
34+
35+
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
36+
- [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/)
37+
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
38+
- [GitHub Help](https://help.github.com)

.github/ISSUE_TEMPLATE.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
#### This issue pertains to:
2+
3+
- [ ] GraphQL Playground - Electron App
4+
- [ ] GraphQL Playground
5+
6+
#### What OS and OS version are you experiencing the issue(s) on?
7+
8+
9+
#### What version of graphql-playground(-electron) are you experience the issue(s) on?
10+
11+
12+
#### What is the expected behavior?
13+
14+
15+
#### What is the actual behavior?
16+
17+
18+
#### What steps may we take to reproduce the behavior?
19+
20+

CODE_OF_CONDUCT.md

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
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.
28+
29+
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.
30+
31+
## Scope
32+
33+
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.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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.
38+
39+
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.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

0 commit comments

Comments
 (0)