add templates for PR/Issues (#150)

* add templates for PR/Issues

* add more structure

* add breaking changes info and update readme

* refactor template a bit

* fix cannotation for :approval:

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,38 @@
+<!-- Please erase any parts of this template not applicable to your issue. -->
+
+##### ISSUE TYPE
+ - [ ] Bug Report
+ - [ ] Feature Idea
+
+# BUG REPORT
+
+##### SUMMARY
+<!-- Briefly describe the problem/enhancement. -->
+
+##### ENVIRONMENT
+* Kubeaudit version: X.Y.Z
+* Kubeaudit install method: DIY-BUILD/Binary/Kubectl-Plugin
+
+##### STEPS TO REPRODUCE
+
+<!-- Please describe exactly how to reproduce the problem. -->
+
+##### EXPECTED RESULTS
+
+<!-- What did you expect to happen when running the steps above? -->
+
+##### ACTUAL RESULTS
+
+<!-- What actually happened? -->
+
+##### ADDITIONAL INFORMATION
+
+<!-- Include any screenshots or other information. -->
+
+# FEATURE IDEA
+
+- [ ] If the maintainers agree with the feature as described here, I intend to submit a Pull Request myself.<sup>1</sup>
+
+**Proposal:** <!-- provide details on the behaviour you'd like to see and why it would be useful -->
+
+<sup><small>1</small></sup> <sub>This is the quickest way to get a new feature! We reserve the right to close feature requests, even ones we like, if the proposer does not intend to contribute to the feature and it doesn't fit in our current roadmap.</sub>

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!-- Please erase any parts of this template not applicable to your Pull Request. -->
+
+<!-- All code PR must be labeled with :bug: (patch fixes), :sparkles: (backwards-compatible features), or :warning: (breaking changes) -->
+
+##### Description
+
+<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->
+
+Fixes # (issue)
+
+##### Type of change
+
+<!-- Please delete options that are not relevant. --->
+- [ ] Bug fix :bug:
+- [ ] New feature :sparkles:
+- [ ] This change requires a documentation update :book:
+- [ ] Breaking changes :warning:
+##### How Has This Been Tested?
+
+<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -->
+
+- [ ] Test A
+- [ ] Test B
+
+##### Checklist:
+
+- [ ] I have :tophat: my changes (A 🎩 specifically includes pulling down changes, setting them up, and manually testing the changed features and potential side effects to make sure nothing is broken)
+- [ ] I have performed a self-review of my own code
+- [ ] I have made corresponding changes to the documentation
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] The test coverage did not decrease

README.md

@@ -513,6 +513,6 @@ If you'd like to fix a bug, contribute a feature or just correct a typo, please
 1. Run the tests to see everything is working as expected: `make test`
 1. Commit your changes: `git commit -am 'Adds awesome feature'`
 1. Push to the branch: `git push fork`
-1. Submit a PR
+1. Submit a PR (All PR must be labeled with :bug: (Bug fix), :sparkles: (New feature), :book: (Documentation update), or :warning: (Breaking changes) )
 1. ???
 1. Profit