added instruction for new PR
@@ -9,6 +9,18 @@ We welcome community contributions to vcf-validator! To build tool locally, foll
New to open source? Here are a selection of issues we've made especially for first-timers. follow this [link](https://github.com/EBIvariation/vcf-validator/issues?q=is%3Aissue+is%3Aopen+label%3Abeginner)
+## Making a New PR
+Once you found an interesting issue to work on you may check if someone other is not working on the same issue. you can ask once in the issue to get that issue assigned to you. once you get an approval go for the PR. While making a new PR do follow these norms:
+
+- Fetch the latest changes by `git fetch upstream`
+- Update the local develop branch `git rebase upstream/develop develop`
+- Create a new branch from develop `git checkout -b <branch_name> develop`
+- Add and commit the changes, commit messages should be short and well explanatory.
+- While creating new PR, change the base from master to develop.
+- PR message should be well explanatory and should contain reference to the issue this PR is for.
+- Once the PR is ready for a review, ask for a review.
+
+
## Bug reports & troubleshooting
If you are submitting a bug, please go to https://github.com/EBIvariation/vcf-validator/issues/new
