Skip to content

Commit 331d7dc

Browse files
authored
Update CONTRIBUTING.md
1 parent 2fe7bd3 commit 331d7dc

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,8 @@
22

33
We really want Parse to be yours, to see it grow and thrive in the open source community.
44

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-
135
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.
146

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-
197
## Setting up the project for debugging and contributing:
208

219
### Recommended setup:
@@ -59,6 +47,8 @@ Once you have babel running in watch mode, you can start making changes to parse
5947

6048
### Please Do's
6149

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.
6252
* 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.
6353
* 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`
6454
* Run the tests for the file you are working on with the following command: `npm test spec/MyFile.spec.js`

0 commit comments

Comments
 (0)