updated CONTRIBUTING.md to point to new coding style guides

google · Nov 20, 2014 · fb15dc4 · fb15dc4
1 parent a80631e
commit fb15dc4
Showing 1 changed file with 7 additions and 4 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -42,17 +42,20 @@ of your first [pull request][].
      issue that you are planning to work on that bug or feature so that it can
      be assigned to you.
 
-  1. Follow the normal process of [forking][] the project, and setup a new
+  2. Follow the normal process of [forking][] the project, and setup a new
      branch to work in.  It's important that each group of changes be done in
      separate branches in order to ensure that a pull request only includes the
      commits related to that bug or feature.
 
-  1. Do your best to have [well-formed commit messages][] for each change.
+  3. Do your best to have [well-formed commit messages][] for each change.
      This provides consistency throughout the project, and ensures that commit
-     messages are able to be formatted properly by various git tools.
+     messages are able to be formatted properly by various git tools. If you 
+     are contributing to the codebase, make sure your code adheres to the 
+     appropriate [style guide][].
 
-  1. Finally, push the commits to your fork and submit a [pull request][].
+  4. Finally, push the commits to your fork and submit a [pull request][].
 
 [forking]: https://help.github.com/articles/fork-a-repo
 [well-formed commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[style guide]: https://github.com/google/physical-web/wiki/Coding-Style-Guides
 [pull request]: https://help.github.com/articles/creating-a-pull-request