Skip to content

Commit 611fd60

Browse files
authored
docs: add CONTRIBUTING.md (#23)
1 parent 6463a3d commit 611fd60

File tree

2 files changed

+62
-2
lines changed

2 files changed

+62
-2
lines changed

CONTRIBUTING.md

+48
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Contributing
2+
3+
Thanks for being willing to contribute!
4+
5+
**Working on your first Pull Request?** You can learn how from this _free_
6+
series [How to Contribute to an Open Source Project on GitHub][egghead]
7+
8+
## Project setup
9+
10+
1. Fork and clone the repo
11+
2. Run `npm ci` to install dependencies
12+
3. Create a branch for your PR with `git checkout -b feature/your-branch-name`
13+
14+
> Tip: Keep your `master` branch pointing at the original repository and make
15+
> pull requests from branches on your fork. To do this, run:
16+
>
17+
> ```
18+
> git remote add upstream [email protected]:smeijer/testing-playground.git
19+
> git fetch upstream
20+
> git branch --set-upstream-to=upstream/master master
21+
> ```
22+
>
23+
> This will add the original repository as a "remote" called "upstream," Then
24+
> fetch the git information from that remote, then set your local `master`
25+
> branch to use the upstream master branch whenever you run `git pull`. Then you
26+
> can make all of your pull request branches based on this `master` branch.
27+
> Whenever you want to update your version of `master`, do a regular `git pull`.
28+
29+
## Committing and Pushing changes
30+
31+
Please make sure to run the tests before you commit your changes. You can run
32+
`npm run test` to do so.
33+
34+
### Linting with git hooks
35+
36+
There are git hooks set up with this project that are automatically installed
37+
when you install dependencies. They're really handy, and will take care of linting
38+
and formatting for you.
39+
40+
## Help needed
41+
42+
Please checkout the [the open issues][issues]
43+
44+
Also, please watch the repo and respond to questions/bug reports/feature
45+
requests! Thanks!
46+
47+
[egghead]: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github
48+
[issues]: https://github.com/smeijer/testing-playground/issues

README.md

+14-2
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,21 @@ Testing-Playground provides you with direct feedback. Trying to visualize the di
1919

2020
## Roadmap
2121

22-
Future ideas are maintained in the [roadmap]. Please use the [issue tracker] to discuss any questions or suggestions you have.
22+
Future ideas are maintained in [roadmap.md]. Please use the [issue tracker] to discuss any questions or suggestions you have.
2323

2424
Every section in the roadmap is accompanied by one or more issues. Contributions are most welcome!
2525

26+
## Contributing
27+
28+
Please see [contributing.md] for more details. If you just want to run the playground on your own machine, go to your terminal and enter the following commands:
29+
30+
```bash
31+
git clone [email protected]:smeijer/testing-playground.git
32+
cd testing-playground
33+
npm ci
34+
npm run start
35+
```
36+
2637
## Contributors
2738

2839
Thanks goes to these people ([emoji key][emojis]):
@@ -47,7 +58,8 @@ Thanks goes to these people ([emoji key][emojis]):
4758
This project follows the [all-contributors][all-contributors] specification.
4859
Contributions of any kind welcome!
4960

50-
[roadmap]: https://github.com/smeijer/testing-playground/blob/master/ROADMAP.md
61+
[roadmap.md]: https://github.com/smeijer/testing-playground/blob/master/ROADMAP.md
62+
[contributing.md]: https://github.com/smeijer/testing-playground/blob/master/ONTRIBUTING.md
5163
[issue tracker]: https://github.com/smeijer/testing-playground/issues
5264
[all-contributors]: https://github.com/all-contributors/all-contributors
5365
[emojis]: https://github.com/all-contributors/all-contributors#emoji-key

0 commit comments

Comments
 (0)