Merge pull request #1667 from public-apis/precise-contributing-guide

Make CONTRIBUTING.md more precise and clear.

CONTRIBUTING.md

@@ -38,13 +38,23 @@ Example entry:
 
 _Without proper [CORS configuration](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) an API will only be usable server side._
 
-Please continue to follow the alphabetical ordering that is in place per section. Each table column should be padded with one space on either side.
+After you've created a branch on your fork with your changes, it's time to [make a pull request][pr-link]. 
 
-If an API seems to fall into multiple categories, please place the listing within the section most in line with the services offered through the API. For example, the Instagram API is listed under `Social` since it is mainly a social network, even though it could also apply to `Photography`.
+*Please follow the guidelines given below while making a Pull Request to the Public APIs*
 
-## Pull Request
+## Pull Request Guidelines
 
-After you've created a branch on your fork with your changes, it's time to [make a pull request][pr-link]!
+* Continue to follow the alphabetical ordering that is in place per section.
+* Each table column should be padded with one space on either side.
+* If an API seems to fall into multiple categories, please place the listing within the section most in line with the services offered through the API. For example, the Instagram API is listed under `Social` since it is mainly a social network, even though it could also apply to `Photography`.
+* Add one link per Pull Request.
+* Make sure the PR title is in the format of `Add Api-name API` *for e.g.*: `Add Blockchain API`
+* Use a short descriptive commit message. *for e.g.*: ❌`Update Readme.md`  ✔ `Add Blockchain API to Cryptocurrency`
+* Search previous Pull Requests or Issues before making a new one, as yours may be a duplicate.
+* Don't mention the TLD(Top Level Domain) in the name of the API. *for e.g.*: ❌Gmail.com ✔Gmail
+* Please make sure the API has proper documentation.
+* Please make sure you squash all commits together before opening a pull request. If your pull request requires changes upon review, please be sure to squash all additional commits as well. [This wiki page][squash-link] outlines the squash process.
+* Target your Pull Request to the `master` branch of the `public-apis`
 
 Once you’ve submitted a pull request, the collaborators can review your proposed changes and decide whether or not to incorporate (pull in) your changes.
 
@@ -57,7 +67,6 @@ merge conflicts will be less likely. See more detailed instructions [here][synci
 * Create a [branch][branch-link] for your edits.
 * Contribute in the style of the project as outlined above. This makes it easier for the collaborators to merge
 and for others to understand and maintain in the future.
-* Please make sure you squash all commits together before opening a pull request. If your pull request requires changes upon review, please be sure to squash all additional commits as well. [This wiki page][squash-link] outlines the squash process.
 
 ### Open Pull Requests
 
@@ -67,11 +76,11 @@ Other contributors and users may chime in, but ultimately the decision is made b
 
 During the discussion, you may be asked to make some changes to your pull request.
 
-If so, add more commits to your branch and push them – they will automatically go into the existing pull request!
+If so, add more commits to your branch and push them – they will automatically go into the existing pull request. But don't forget to squash them.
 
 Opening a pull request will trigger a Travis CI build to check the validity of all links in the project. After the build completes, **please ensure that the build has passed**. If the build did not pass, please view the Travis CI log and correct any errors that were found in your contribution. 
 
-Thanks for being a part of this project, and we look forward to hearing from you soon! 
+*Thanks for being a part of this project, and we look forward to hearing from you soon!* 
 
 [branch-link]: <http://guides.github.com/introduction/flow/>
 [clone-link]: <https://help.github.com/articles/cloning-a-repository/>