Merge pull request #255 from pattern-lab/dev

added .github dir and templates

Author: Brian Muenzenmeyer

CONTRIBUTING.md renamed to .github/CONTRIBUTING.md

@@ -1,12 +1,12 @@
-#Contributing to Patternlab - Node
-If you'd like to contribute to patternlab - node, please do so! There is always a lot of ground to cover, with patternlab - php being so feature-rich.  
+# Contributing to Patternlab Node
+If you'd like to contribute to Pattern Lab Node, please do so! There is always a lot of ground to cover and something for your wheelhouse.  
 
-No pull request is too small. Check out any [up for grabs issues](https://github.com/pattern-lab/patternlab-node/labels/up%20for%20grabs) as a good way to get your feet wet. 
+No pull request is too small. Check out any [up for grabs issues](https://github.com/pattern-lab/patternlab-node/labels/up%20for%20grabs) as a good way to get your feet wet, or add some more unit tests.
 
-##Guidelines
-1. Please keep your pull requests concise and limited to **ONE** substantive change at a time.
-2. _ALWAYS_ submit pull requests against the [dev branch](https://github.com/pattern-lab/patternlab-node/tree/dev). If this does not occur, I will first, try to redirect you gently, second, port over your contribution manually if time allows, and/or third, close your pull request.
-3. If you can, add some unit tests using the existing patterns
+## Guidelines
+1. Please keep your pull requests concise and limited to **ONE** substantive change at a time. This makes reviewing and testing so much easier.
+2. _ALWAYS_ submit pull requests against the [dev branch](https://github.com/pattern-lab/patternlab-node/tree/dev). If this does not occur, I will first, try to redirect you gently, second, port over your contribution manually if time allows, and/or third, close your pull request. If you have a major feature to stabilize over time, talk to @bmuenzenmeyer about making a dedicated `feature-branch`
+3. If you can, add some unit tests using the existing patterns in the `./test` directory
 
 ##Coding style
 Regarding code style like indentation and whitespace, follow the conventions you see used in the source already. Add enough source code comments to help the next person.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,9 @@
+I am using Pattern Lab Node `vX.X.X` on `Windows|Mac|Linux`, using the `grunt|gulp` configuration.
+
+##### Expected Behavior
+
+
+##### Actual Behavior
+
+
+##### Steps to Reproduce

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,5 @@
+**Target the `dev` branch!**
+
+Addresses #
+
+Summary of changes: