|
2 | 2 |
|
3 | 3 | We really want Parse to be yours, to see it grow and thrive in the open source community. |
4 | 4 |
|
5 | | -Before you jump into the coding element of contributing, please make sure you first [open an issue](https://github.com/parse-community/parse-server/issues/new/choose) relating to your contribution, or continue the discussion in the existing issue. |
6 | | - |
7 | | -This helps us all plan out the best conceptual approach for the contribution, so that your time isn't wasted on approaches or features that could be tackled in a different way. Our team are also happy to give you pointers and suggestions to speed up the process. |
8 | | - |
9 | | -When opening an issue, please make sure you follow the templates and provide as much detail as possible. |
10 | | - |
11 | | -After you've completed the contribution, you'll need to submit a Pull Request (PR). |
12 | | - |
13 | 5 | If you are not familiar with Pull Requests and want to know more about them, you can visit the [Creating a pull request](https://help.github.com/articles/creating-a-pull-request/) article. It contains detailed informations about the process. |
14 | 6 |
|
15 | | -If you need any help along the way, you can open a Draft PR where we can help finalize your contribution. |
16 | | - |
17 | | -Contributing can be challenging, so don't be discouraged if you're having difficulties. Please don't hesitate to ask for help. |
18 | | - |
19 | 7 | ## Setting up the project for debugging and contributing: |
20 | 8 |
|
21 | 9 | ### Recommended setup: |
@@ -59,6 +47,8 @@ Once you have babel running in watch mode, you can start making changes to parse |
59 | 47 |
|
60 | 48 | ### Please Do's |
61 | 49 |
|
| 50 | +* Before you jump into the coding element of contributing, please make sure you first [open an issue](https://github.com/parse-community/parse-server/issues/new/choose) relating to your contribution, or continue the discussion in the existing issue. |
| 51 | +* Feel free to ask the team or community for assistance with your contribition. If needed, you can open a Draft PR where we can help finalize your contribution. |
62 | 52 | * Begin by reading the [Development Guide](http://docs.parseplatform.org/parse-server/guide/#development-guide) to learn how to get started running the parse-server. |
63 | 53 | * Take testing seriously! Aim to increase the test coverage with every pull request. To obtain the test coverage of the project, run: `npm run coverage` |
64 | 54 | * Run the tests for the file you are working on with the following command: `npm test spec/MyFile.spec.js` |
|
0 commit comments