Issue and PR templates for github

Modeled after the templates used in the elasticsearch repo, these
templates will be used by github to prefill issue and pull request
bodies to help users avoid commonly encountered problems.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,36 @@
+<!--
+GitHub is reserved for bug reports and feature requests. The best place
+to ask a general question is at the Elastic Discourse forums at
+https://discuss.elastic.co. If you are in fact posting a bug report or
+a feature request, please include one and only one of the below blocks
+in your new issue.
+-->
+
+<!--
+If you are filing a bug report, please remove the below feature
+request block and provide responses for all of the below items.
+-->
+
+**Kibana version**:
+
+**OS version**:
+
+**Original install method (e.g. download page, yum, from source, etc.)**:
+
+**Description of the problem including expected versus actual behavior**:
+
+**Steps to reproduce**:
+ 1.
+ 2.
+ 3.
+
+**Errors in browser console (if relevant)**:
+
+**Provide logs and/or server output (if relevant)**:
+
+<!--
+If you are filing a feature request, please remove the above bug
+report block and provide responses for all of the below items.
+-->
+
+**Describe the feature**:

.github/PR_TEMPLATE.md

@@ -0,0 +1,13 @@
+<!--
+Thank you for your interest in and contributing to Kibana! There
+are a few simple things to check before submitting your pull request
+that can help with the review process. You should delete these items
+from your submission, but they are here to help bring them to your
+attention.
+-->
+
+- Have you signed the [contributor license agreement](https://www.elastic.co/contributor-agreement)?
+- Have you followed the [contributor guidelines](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md)?
+- If submitting code, have you included unit tests that cover the changes?
+- If submitting code, have you tested and built your code locally prior to submission with `npm test && npm run build`?
+- If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.